@dev.trystops.xyz
this is about to save me so much money though
April 21, 2025 at 5:19 AM
this is about to save me so much money though
now if I'm right that everything else is working we're just in a classic lag burndown situation -- might temporarily scale up to a larger instance type to see if that can process faster
April 19, 2025 at 11:36 PM
now if I'm right that everything else is working we're just in a classic lag burndown situation -- might temporarily scale up to a larger instance type to see if that can process faster
the cause for that turned out to be cpu throttling on the shared instance type I was using -- I'd get 100% CPU performance for a few minutes at startup, then exhaust credits and call back down to 1/16th of a vcpu which would also drop the throughput of the firehose processing
April 19, 2025 at 11:34 PM
the cause for that turned out to be cpu throttling on the shared instance type I was using -- I'd get 100% CPU performance for a few minutes at startup, then exhaust credits and call back down to 1/16th of a vcpu which would also drop the throughput of the firehose processing
think I found the culprit for at least one of these problems. was seeing a lot of graphs that looked like the one attached -- spike in throughput at startup, then dropping down to a low baseline. not a pattern I was seeing on my laptop either
April 19, 2025 at 11:34 PM
think I found the culprit for at least one of these problems. was seeing a lot of graphs that looked like the one attached -- spike in throughput at startup, then dropping down to a low baseline. not a pattern I was seeing on my laptop either
feed still seems to be misbehaving but check out that latency improvement yesterday
April 19, 2025 at 8:23 PM
feed still seems to be misbehaving but check out that latency improvement yesterday
