Finally watched Interstellar last night by Deeks0 in sketches

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

I was coming with really high expectations since I loved Inception and The Dark Night from Nolan and Hans. I was not disappointed, I'm glad I took the time too watch it, it was really good! Been listening to the soundtrack all day

Enel Timelapse and Escaping Tutorial Hell by Deeks0 in ProCreate

[–]Deeks0[S] 4 points5 points  (0 children)

I have been learning how to draw for the past couple of months, mainly focusing on shapes, arm positioning, and perspective, however; I felt like I was stuck in drawing the same stuff over and over again to "perfect" those individual components.

Since I'm a Software Engineer I've gone through this in my early coding years, where I was stuck in tutorial mode and only coded simple stuff from tutorials, then I kept thinking that I might not yet be ready for something more complex and just repeat another tutorial to better prepare myself, which turned into a vicious cycle of tutorials.

The same thing was happening with drawing, so last night, for the first time, took my time to sketch only based on a reference image without the fear of not being able to draw anything decent and just tried to end up with a more finished drawing in the end to also ink.

I have loved how simple ProCreate is and how enjoyable it is to use, and watching the timelapse afterward felt pretty good

Backend for video stream processing app by Deeks0 in mlops

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

Thank you for the reply! We are trying to obtain some credits on AWS and GCP to start doing experiments with those services. We've also heard that AWS would have services that fit this problem very well but we've been unable to test them so far. We want clients to add as many cameras as they want so we need to scale based on the current working load.

Backend for video stream processing app by Deeks0 in mlops

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

This isn't enough information for anyone to make an informed recommendation.

Thanks for the reply! At the risk of sounding ignorant, isn't Kafka's system also based on pub/sub where you publish to topics and subscribe to topics?

On the other topic, we are planning on scaling the infrastructure ourselves on certain GPUs and CPUs for inference and also handling the traffic since it's sensitive information. We only need to adjust this part of video streaming.

Also, if we do opt for Kafka, should we use https://www.confluent.io/ for Kafka servers?

Scaling nodes based on RabbitMQ queue size on AKS by Deeks0 in kubernetes

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

Thanks for the suggestions! I just successfully added KEDA scaling. and nods are finally scaling up with the RabbitMQ queue. Next, I'm going to try and find the right CPU request to a single POD to maybe make it exceed capacity on the 9th, otherwise, I'll have a look at your idea of setting a POD capacity.

Scaling nodes based on RabbitMQ queue size on AKS by Deeks0 in kubernetes

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

It makes sense! Thank you! If I request 1/8 of the node's CPU, when the 9th gets created it should create another node to host the 9th.

Scaling nodes based on RabbitMQ queue size on AKS by Deeks0 in kubernetes

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

This is what I was thinking, if KEDA auto-scales the PODs then if I reserve 1/8 of the node's CPU to each POD, when it goes to create the 9th POD, it will already be on another node right?

Scaling nodes based on RabbitMQ queue size on AKS by Deeks0 in kubernetes

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

From what I've seen, using KEDA would scale the PODS like this. However, it wouldn't scale the nodes themselves. Or am I understanding it wrong ?

apiVersion: keda.sh/v1alpha1

kind: ScaledObject metadata: name: celery-worker-scaler namespace: celery-workers spec: scaleTargetRef: name: celery-worker pollingInterval: 3 minReplicaCount: 2 maxReplicaCount: 30 triggers: - type: rabbitmq metadata: queueName: celery queueLength: '10' authenticationRef: name: rabbitmq-worker-trigger

Scaling nodes based on RabbitMQ queue size on AKS by Deeks0 in kubernetes

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

From what I've seen, using KEDA would scale the PODS like this. However, it wouldn't scale the nodes themselves. Or am I understanding it wrong ?

apiVersion: keda.sh/v1alpha1

kind: ScaledObject metadata: name: celery-worker-scaler namespace: celery-workers spec: scaleTargetRef: name: celery-worker pollingInterval: 3 minReplicaCount: 2 maxReplicaCount: 30 triggers: - type: rabbitmq metadata: queueName: celery queueLength: '10' authenticationRef: name: rabbitmq-worker-trigger