According to the article, Pyramid pushes a lot of work to C code. But then they measure relative performance by how much output the Python profiler has. However anything done in C is invisible to the Python profiler. That means that time is being spent and work is being done that they are not measuring.
The result is probably pretty fast. But I strongly doubt it is faster by the factor that their numbers claim.
According to the article, Pyramid pushes a lot of work to C code. But then they measure relative performance by how much output the Python profiler has. However anything done in C is invisible to the Python profiler. That means that time is being spent and work is being done that they are not measuring.
The result is probably pretty fast. But I strongly doubt it is faster by the factor that their numbers claim.