The bug.
Nikita Konovalov tested the empty stack with 10 nodes(3+7) and got this results: https://docs.google.com/spreadsheets/d/1Ds9eKQ5uSPmZdg-NwtX1WWBHb5JE9Q9mOyQl0ZSZhN4/edit#gid=0
For example, 100 elements render on page costs 6.5 secs and 200 elements render costs 13.1 secs. I think, as a perf engineer, that its slow. So this is one more constatations of this bug for me.
As I know measuring was performing without ssl.
Test env on every note:
CPU 12 x 2.10 GHz
Memory 2 x 16.0 GB, 32.0 GB total
I must say that some engineers try to fix this problem in some way, like Anton Chevychalov on MOS7, but they do it separately, as I can see. I guess that this bug wouldn't be fixed in near future in that way.
The profiler.
Also, there are some problems with tries to install correctly working Profiler. I got instructions how to install it in condition that can store infromation on db. I'll try it in next few days.
Hello.
The bug. /docs.google. com/spreadsheet s/d/1Ds9eKQ5uSP mZdg-NwtX1WWBHb 5JE9Q9mOyQl0ZSZ hN4/edit# gid=0
Nikita Konovalov tested the empty stack with 10 nodes(3+7) and got this results:
https:/
For example, 100 elements render on page costs 6.5 secs and 200 elements render costs 13.1 secs. I think, as a perf engineer, that its slow. So this is one more constatations of this bug for me.
As I know measuring was performing without ssl.
Test env on every note:
CPU 12 x 2.10 GHz
Memory 2 x 16.0 GB, 32.0 GB total
I must say that some engineers try to fix this problem in some way, like Anton Chevychalov on MOS7, but they do it separately, as I can see. I guess that this bug wouldn't be fixed in near future in that way.
The profiler.
Also, there are some problems with tries to install correctly working Profiler. I got instructions how to install it in condition that can store infromation on db. I'll try it in next few days.