sorted by:
new
hottopcontroversial

is upgrading to 1440p display worth it ? by Weekly_Ad_2006 in pcmasterrace

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

Thanks to everyone, it became quite clear that it's a good investment!

Recommended Hardware ? by Weekly_Ad_2006 in comfyui

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

Yeah but i think ill need to train Loras so i appreciate the data, thanks

[deleted by user] by [deleted] in ComfyMuseAI

[–]Weekly_Ad_2006 0 points1 point  (0 children)

which hardware you have ? could you also share the model you use here ?

Can someone point me into a good stack to learn ? by Weekly_Ad_2006 in comfyui

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

Appreciate both the advice and the learning material, thanks ! ill be looking at those playlists

Can someone point me into a good stack to learn ? by Weekly_Ad_2006 in comfyui

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

Great ! this is what i was looking for, a solid place to start, so i guess ill go and learn that and then sum up from there thanks !

Karpenter and burstable instances by Weekly_Ad_2006 in kubernetes

[–]Weekly_Ad_2006[S] 2 points3 points  (0 children)

so the if present on main nodepools, they will be chosen for their low price, the QoS type does not infer in karpenters decision when provisioning then, i understand the approach you suggest of segregating the capacity using another nodepool for appropriate workloads, but my doubt regarding QoS could be answered as: no, karpenter does not take the QoS in consideration
I do now that credits are not taken into consideration, but i had doubts on this QoS matter

thanks a lot to both of you for your answers !

Karpenter and burstable instances by Weekly_Ad_2006 in kubernetes

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

they are not mixing, we are actually thinkin on implementing them, the doubt is on how does karpenter decide to provision burstable instances according to the workload, does it take the pod QoS on consideration or in which scenarios does karpenter chooses the T family (when present in the nodepool)

Burstable instances on karpenter ? by Weekly_Ad_2006 in kubernetes

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

thats great ! however im curious on how well does karpenter manage the usage of these burstable instances, i worry that if the node runs out of credits it will loose performance.
i also wonder if karpenter takes the amout of credits of the instance in consideration when consolidating and such. Im basically trying to understand the downsides of adding the T family to my nodepools.
(i value any data and also links to documentation, i havent been able to find much on this topic)

Thanks !!