lomkju

Just In RAM prices have crashed got a weekly price update from a vendor for DDR5 64GB RDIMM 10X cheaper than last week!!

Causes TurboQuant and AI Market leader backing out from their RAM purchasing commitment!!

Toughest captcha I have ever solved in my lifetime.

Nice! Can this support any cloud like Kamal does? Can I somehow use this on Excloud?

Nice! Have you looked into using AI agents for reverse engineering? I would like to know if that would be possible.

Even humans get confused with trick questions right? Once they understand this is a trick question they no longer fall for it. :)

I feel the GPU restrictions created an environment for Chinese Devs to be more innovative and do more with less.

Kudos to the deepseek team!

Nice!

Could you tell me why Google Drive didn’t work for you?

Google Drive seems to cheaper and has better UX than S3 - $8 for 2 TB (India) - Supports file versioning - 750GB bandwidth per day

We don't have terraform right now, will be releasing it soon.

You can use our CLI which is built on our SDK written in GO.

Thanks, hope you got a chance to use the free VM.

Makes sense. Thanks for your advice.

> Just FYI, we also have simple helm charts, and the repository is hosted on https://vinceanalytics.com/charts

Oh cool, didn't see that in the docs.

> Does it always pull the latest vince image?

Yes haven't specified any tag so should default to latest.

Nice Work! Very easy to install and use.

I deployed this on our cloud (excloud.in) in less than 2 mins.

Anyone you can use the below k8s manifest to deploy it to their k8s cluster. Just change the admin password before doing so.

https://gist.github.com/lomkju/90fe7500d8cf854bf3b7c2f26aa58...

Having being a high scale AWS user with a bill of +$1M/month and now working since 2 years with a company which uses GCP. I would say AWS is superior and way ahead.

** NOTE: If you're a low scale company this won't matter to you **

1. GKE

When you cross a certain scale certain GKE components won't scale with you and SLOs on those components are crazy, it takes 15+ mins for us to update a GKE ingress controller backed Ingress.

Cloud Logging hasn't been able to keep up with our scale, disabled since 2 years now. This last Q we got an email from them to enable it and try it again on our clusters, still have to confirm these claims as our scale is more higher now.

Konnectivity agent release was really bad for us, it affected some components internally, total dev time we lost was more than 3 months debugging this issue. They had to disable konnectivity agent on our clusters, I had to collect TCP dumps and other evidences just to prove nothing was wrong on our end, fight with our TAM to get a meeting with the product team. After 4 months they agreed and reverted our clusters to SSH tunnels. Initially GCP support said they said they can't do this. Next Q Ill be updating the clusters hopefully they have fixed this by then.

2. Support.

I think AWS support always were more pro active in debugging with us, GCP support agents most of the times lack the expertise or proactiveness to debug/solve things in simple cases. We pay for enterprise support and don't see getting much from them. At AWS we had reviews of the infra how we could better it every 2 Qs and we got new suggestion and was also the time when we shared what we would like to see in their roadmap.

3.Enterprisyness is missing with design

A simple thing as cloudbuild doesn't have access to static IPs. We have to maintain a forward proxy just cause of this.

L4 LBs were a mess you could only use specified ports in a (L4 LB) TCP proxy, For a tcp proxy based loadbalancer, the allowed set of ports are - [25, 43, 110, 143, 195, 443, 465, 587, 700, 993, 995, 1883, 3389, 5222, 5432, 5671, 5672, 5900, 5901, 6379, 8085, 8099, 9092, 9200, and 9300]. Today I see they have removed these restrictions. I don't know who came up with this idea to allow only a few ports on a L4 LB. I think such design decisions make it less Enterprisy.

Now waiting for Netflix to make a movie about this .

Thanks!

They so need to apply this to Google Maps, in India google maps has gone crazy since past 2 years especially in Mumbai. It seems to give all bad routes always and also all gig workers in Uber, Ola, Swiggy, Zomato are affected by this too.

Will do thanks!

How to beat rainbow tables, add some salt.

This only makes sense if the local I/O is really fast and in many cases you contact external databases where the context switches are negligible to the I/O time spent on a query.

This looks a bit like portainer https://github.com/portainer/portainer

dd is just 79K

As simple as

sudo dd if=name-of-iso.iso of=/dev/sdb status="progress"

https://medium.com/@tbeach/use-unix-dd-command-to-os-bootabl...

You're Welcome.

You can't test everything in production.

Be it an infra change or application. It should always be like:

Staging -> Canary -> Production

If you invest time in making the above pipeline automated it will cause less outages.

P.S we use feature flags but it won't solve many other challenges around infra and application changes.

Some examples: - Changing from Classic ELBs to ALBs (We care about latencies so ALBs served 1% traffic in the start) - Zero downtime single mysql master upgrade. (ProxySql) - New k8s controllers. - New metrics adapters.

Staging should be like a playground to test all edge cases before you go to canary and then to prod.

Makes sense. Comparing the pricing with AWS lambda fly.io is way cheaper. Will give it a try :)