If you're not using memcached, that will be a huge gain. -David
On Wed, Mar 3, 2010 at 3:37 PM, Christian Hammond <chip...@chipx86.com> wrote: > A lot of what Review Board does is computationally expensive, and we've done > a lot to heavily optimize things. Best way to get speedup is to run it on a > faster server with more memory and more caching. We don't support anything > like psyco or other accelerators. > > Christian > > -- > Christian Hammond - chip...@chipx86.com > Review Board - http://www.reviewboard.org > VMware, Inc. - http://www.vmware.com > > > On Wed, Mar 3, 2010 at 4:01 AM, JohnHenry <qhlonl...@163.com> wrote: >> >> Hi,all >> We want the reviewboard to run faster. We found that on some >> functions like view_diff and view "All review reqeusts", the "cpu >> consume" on apache (Reviewboard server) cost 90%, and less then 10% on >> MySQL, So it seems that the bottleneck is not lie in Too Much SQL >> Execution. We tried acclerator like "psyco", But it will cause web >> page breakdown on ReviewBoard. So Is there any speed up method for us? >> If the CPU is the bottleneck, will memcached help to speed up? >> >> Another problem is that some times, When we create review request >> with post-review, It will faild with a bad page saying >> -------------------------------- >> Unable to access >> http://192.168.3.155:8080/api/json/reviewrequests/163/publish/. >> The host path may be invalid HTTP Error 500: Internal Server Error >> ------------------------------- >> and the page title is: >> ------------------------------------ >> SMTPServerDisconnected at /api/json/reviewrequests/163/publish/ >> Connection unexpectedly closed >> ----------------------------------- >> I want to know the reason of this problem. If the problem is that >> our mail server is too busy, Then this will affect nothing of >> ReviewRequest publishing, Why it will report "Unable to access >> http://192.168.3.155:8080/api/json/reviewrequests/163/publish/";; How >> to distinguish this with the real happening of Unable to access ? >> And, If possible, I want a list of post-review exceptions and >> reasons. so that we will deal with those exceptions when do >> automation. >> >> Best Regards! >> >> Best Regards! >> >> -- >> Want to help the Review Board project? Donate today at >> http://www.reviewboard.org/donate/ >> Happy user? Let us know at http://www.reviewboard.org/users/ >> -~----------~----~----~----~------~----~------~--~--- >> To unsubscribe from this group, send email to >> reviewboard+unsubscr...@googlegroups.com >> For more options, visit this group at >> http://groups.google.com/group/reviewboard?hl=en > > -- > Want to help the Review Board project? Donate today at > http://www.reviewboard.org/donate/ > Happy user? Let us know at http://www.reviewboard.org/users/ > -~----------~----~----~----~------~----~------~--~--- > To unsubscribe from this group, send email to > reviewboard+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/reviewboard?hl=en -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~----------~----~----~----~------~----~------~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
