© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
@Brian Rosmaita
"I think the slowdown is from stuffing all those chars into JSON when generating the response, not from the way the data is stored in the DB"
About this, you are right. I wrote a script to test reading data directly from DB and found that there was not much latency. However, when reading data from Horizon, the CPU usage of the backend Apache2 server reached 100%.
“but I don't think the performance issue was discussed in that thread.....,I think the slowdown issue is something we should take seriously,”
@fungi and @brian-rosmaita
Should we create a thread on Horizon to discuss this issue? In my opinion, Horizon does not need to read and return all the additional properties to the user? Horizon can choose to only return the additional properties (i.e., descriptions) that Horizon is capable of modifying, thus Horizon will not be affected by the length of properties .
In general, I believe Horizon should protect itself instead of relying on Glance.