Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Revisions: Issue #32104 All Revisions ] Back to Issue ]
Summary 0032104: [RR16Q1][HighVol] Create many search requests induces postgres processes jam the cpu of the machine
Revision 2016-02-03 13:26 by lorenzofidalgo
Steps To Reproduce 0-Log to the server machine and use "top" command to control the CPU usage of the server machine.
1-In a HighVol configured machine, login POS to CMS-1, VBS-1 and PS-1 with different devices/PCs to do the following testing:
2-Go with all the terminals to "Seach" tab and throw as many requests as you can clicking many times search (magnifier) button. Change the requests choosing different filters, like entering some strings or choosing different categories like "Backpack & travel" or "Lighting & Electronics".
3-After some time executing this queries, check the usage of the server machine (step 0): Many postgres processes that will not finish have been created. Even after login out with all terminals, those processes are still there.
Revision 2016-02-03 13:26 by lorenzofidalgo
Steps To Reproduce 0-Log to the server machine and use "top" command to control the CPU usage of the server machine.
1-In a HighVol configured machine, login POS to CMS-1, VBS-1 and PS-1 with different devices/PCs to do the following testing:
2-Go with all the terminals to "Seach" tab and throw as many requests as you can clicking many times search (magnifier) button. Change the requests choosing different filters, like entering some strings or choosing different categories like "Backpack & travel" or "".
3-After some time executing this queries, check the usage of the server machine (step 0): Many postgres processes that will not finish have been created. Even after login out with all terminals, those processes are still there.


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker