Re:Actix-web 1.0 – A small, pragmatic, and fast web framewor...
by abetlen on Wednesday June 05, 2019 @05:04PM
(#20109124)
Not OP but to answer #2, based on the benchmark code here [1] the difference is that actix-pg accesses the database through message passing in the actor system [2] while actix-core accesses it directly [3].
[1]. https://github.com/TechEmpower/FrameworkBenchmarks/tree/mast...
[2]. https://github.com/TechEmpower/FrameworkBenchmarks/blob/mast...
[3]. https://github.com/TechEmpower/FrameworkBenchmarks/blob/mast...
Re:Actix-web 1.0 – A small, pragmatic, and fast web framewor...
by continuations on Wednesday June 05, 2019 @05:15PM
(#20109235)
I clicked on the "latency" tab of the benchmarks result [1] and there's a big difference in maximum latency between the 2 approaches:
actix-pg: 27.1 ms
actix-core: 201.1 ms
Is that to be expected?
[1] https://www.techempower.com/benchmarks/#section=test&runid=9...
1. What is the reason for rewriting the framework to abandon actors in favor of services?
2. In the Tech Empower benchmarks, what's the difference between actix-core and actix-pg? What caused the difference in performance between the 2?
3. What's your experience with using actix-web in production? How does it compare to other frameworks you've used?
Thanx