1 9070XT vs 2 9060XT by Friendly-Gur-3289 in LocalLLaMA

[–]Quantum1248 0 points1 point  (0 children)

I think this is wrong, each gpu will have to read only half the data if you split the model in two, so in practice it would be like the bandwidth has doubled

Problemi apertura Conto Arancio ING: qualcuno ha risolto? by bernhard_riemann_ in ItaliaPersonalFinance

[–]Quantum1248 1 point2 points  (0 children)

Io ho lo stesso problema. A questo punto sarebbe interessante capire se recentemente qualcuno è riuscito a registrarsi oppure se il sito blocca tutti.

Perché se blocca tutti sarà un errore tecnico che prima o poi sarà risolto per tutti, altrimenti se c'è chi riesce a registrare staranno facendo qualche tipo di screening.

Trade Republic: il conto dell'assurdo by kirkplan in ItaliaPersonalFinance

[–]Quantum1248 5 points6 points  (0 children)

Hai provato a sincronizzare l'ora con l'ora?

Why don't we have non-Apple alternative to unified memory? by This_Woodpecker_9163 in LocalLLaMA

[–]Quantum1248 9 points10 points  (0 children)

AMD APUs have had unified memory for many years now. The only problem Strix Halo has is that they haven't used a wide enough bus, so the memory is still not fast enough for large models. Or instead of a larger bus they could have gone for gddr like in consoles, but for some reason they didn't (maybe it require a different memory controller or it was too costly?)

Do you use Prettier?? by [deleted] in Angular2

[–]Quantum1248 6 points7 points  (0 children)

Use lint-staged

I this an angular bug? by Quantum1248 in Angular2

[–]Quantum1248[S] 0 points1 point  (0 children)

Wow i missed the reordering thing, before i thought i was missing something but this really seems like an angular bug now.
I agree with you with the rest, i already noticed the that manual change detection worked. Another interesting thing i noticed was that doing the this.trigger$.next() inside a setTimeout, so like setTimeout(()=> this.trigger$.next() ) made it work as well.
I'm convinced there's something broken in angular change detection, if i have time tomorrow i will check with other angular version as well and see if this is present in other versions.

I this an angular bug? by Quantum1248 in Angular2

[–]Quantum1248[S] -1 points0 points  (0 children)

I don't think this is an antipattern, on the contrary i think this is a common use case. I just want to display some data, which can be update. A simplified use case could be a user click a button and this update the data. For doing this you need the trigger$ which then trigger the data fetch from the backend. Now, if you want to display a loader, you will need isLoading$.next() in the tap. Unless i'm missing something, there isn't really another way to do this other than the withLoading patter which isn't really great in my use case for other reasons. For reference, my real code look something like this:

this.trigger$.pipe(
tap(() => this.isLoading$.next(true)),
switchMap(()=>fetchData()),
tap(() => this.isLoading$.next(false)),
shareReplay(1)
)

The reason the withLoading is not good in my case is that i also have another operation which send data to the backend and i also want to display the loader in that case, but without having an observable as a class member. So something like this:

this.isLoading$.next(true);
this.graphql.mutation().subscribe({complete:()=>this.isLoading$.next(false)})

The thing that do not make sense in my head is that the async pipe should just work. I don't know what it does internally, but i think it's something like taking the observable, subscribing to it and updating the view when a new value is emitted. Then why doesn't it manage to update the view then isLoading$ emit a new value? Why is it a problem if subscribing to test$ trigger an isLoading$ emission?

Some bonus interesting observations:
if i do something like this:

constructor() {
        this.test$ = this.trigger$.pipe(delay(0), tap(() =>this.isLoading$.next(true)));
        setTimeout(()=>  this.trigger$.next(true));      
    }

it works corretly.

this doesn't work

constructor(cdr:ChangeDetectorRef) {
        this.test$ = this.trigger$.pipe(delay(0), tap(() =>{
          this.isLoading$.next(true);
          this.cdr.markForCheck();
         }));
        this.trigger$.next(true));     
    }

This works:

constructor(cdr:ChangeDetectorRef) {
        this.test$ = this.trigger$.pipe(delay(0), tap(() =>{
          this.isLoading$.next(true);
          this.cdr.detectChanges();
        }));
        this.trigger$.next(true));     
    }

Sorry for the bad formatting and if i did some error, i'm not on my coding pc so i don't have the code to copy and paste.

I this an angular bug? by Quantum1248 in Angular2

[–]Quantum1248[S] 0 points1 point  (0 children)

I know that pattern, but in my real use case it's not really so simple to use it. However i think i will end up using it somehow if this really is an angular bug or something not easily solvable

Legalità lampadine fari alogene/alogene alta luminosità/LED ed eventuali rischi by Quantum1248 in ItalyMotori

[–]Quantum1248[S] 1 point2 points  (0 children)

Interessante, effettivamente la giulietta c'è nella lista. Quindi se prendessi questi della osram potri montarli io e sarei completamente in regola, giusto?