24 ms·
A major issue with loom is that it consume much more %CPU https://github.com/ebarlas/project-loom-comparison/blob/main/docs/comparison-plots.png https://github.
by SemanticStrengh 4y ago
A major issue with loom is that it consume much more %CPU
https://github.com/ebarlas/project-loom-comparison/blob/main/docs/comparison-plots.png https://github.com/ebarlas/project-loom-comparison/blob/main...
Edit no it is more efficient although it consume surprisingly high gpus at higher throughput than the others.
- brokencode 4y agoLooking at the graphs, it uses less CPU for a given throughout, so it’s actually more efficient for CPU. It also provides lower latency and higher max throughout. It does seem to require more memory, though.
- pron 4y agoWe expect to improve the memory consumption significantly in future releases. Some things had to be cut to make this release.
- SemanticStrengh 4y agoThe existing data already looks excellent. I wonder if you could leverage SIMD/the vector api for speeding up some things. Or if value types will have an impact.
- didibus 4y agoWouldn't that be expected when it also delivers more throughput and better latencies? It's handling more requests concurrently, so I'd expect the CPU usage to be higher, how else could it serve more requests faster otherwise?
- SemanticStrengh 4y agoYes indeed I just find the consumption increase a but abrupt after 10K