Causes TurboQuant and AI Market leader backing out from their RAM purchasing commitment!!
115 karma · joined April 23, 2020
https://www.linkedin.com/in/arjun-hemrajani-416581ab/
Causes TurboQuant and AI Market leader backing out from their RAM purchasing commitment!!
Kudos to the deepseek team!
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
You can use our CLI which is built on our SDK written in GO.
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.
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...
** 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.
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.
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.
We have complex flows where we use Slack, Spinnaker(Webhooks), Terraform, PagerDuty ... and much more.
Is there something better that we can achieve with this?
micro-2x shared 512MB $0.000003044 $8 VS t3a.nano 2 Variable 0.5 GiB EBS Only $0.0031 per Hour
I'm missing something? cause seeing the pricing I still feel AWS is cheaper.