Updating to a new Hudson version is being discussed in bug 371039 https://bugs.eclipse.org/bugs/show_bug.cgi?id=371039
So far, trending towards 2.2 ... but, I'm sure others view would be helpful (Especially Hudson team :) Thanks, From: Jesse McConnell <[email protected]> To: Cross project issues <[email protected]>, Date: 02/16/2012 10:58 AM Subject: Re: [cross-project-issues-dev] Hudson sluggishness Sent by: [email protected] I just saw a tweet about 3.0.0 milestone being released from eclipse with lots of fixes and features... would updating to this release perhaps help? cheers, jesse -- jesse mcconnell [email protected] On Thu, Feb 16, 2012 at 09:46, Konstantin Komissarchik <[email protected]> wrote: > In my experience, Hudson's ability to directly serve artifacts efficiently > and fast is very weak. This appears to be an issue with Hudson servlet that > isn't going to be alleviated by changing containers. Hudson's download > support has further limitation of not supporting resume, which further > impacts performance. > > I have made a weak workaround for this issue in the Hudson cluster that I > administer by letting the container serve artifacts directly from disk > (bypassing Hudson servlet). We use Tomcat to host Hudson and to serve the > artifacts on a side (different base URL). The performance difference between > these two download entry points is astonishing even under moderate loads. Of > course (at least in our naïve implementation), you lose many benefits > afforded by downloading via Hudson URL's, such as having a singular last > good URL to reference. This is something that could be improved by someone > with a bit of time and working PHP knowledge... > > HTH, > > - Konstantin > > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of > Webmaster(Matt Ward) > Sent: Thursday, February 16, 2012 7:21 AM > To: Cross project issues > Subject: [cross-project-issues-dev] Hudson sluggishness > > Hi Folks, > > I just wanted to share a comment with you from the Hudson team based on > their investigation yesterday of the poor Hudson performance: > > >The reason why Hudson is dead slow is someone is trying to download > entire artifacts via HTTP (either via wget or curl). Winstone container is > working hard to satisfy the request and on the process it has created > 363 handling threads. See below. >Winstone container is not meant for such > kind of handling. If any one wants to get artifacts ask them to get it > directly from the disk, not via HTTP request to Hudson like this other wise > it will kill the container > > So if you could take a look at your jobs(I understand it might be next week > sometime) and make sure you're only using HTTP(to fetch Hudson > objects) if it's really needed that would be great. > > Now, we are planning to move to Jetty so hopefully that will alleviate some > of this. However it got Denis and I wondering if any of you with access to > a large Hudson deployment could tell us what container software it's using. > > -Matt. > > -- > > Eclipse WebMaster - [email protected] > > Questions? Consult the WebMaster FAQ at > http://wiki.eclipse.org/index.php/Webmaster_FAQ > View my status at http://wiki.eclipse.org/index.php/WebMaster > > EclipseCon 2012 <http://www.eclipsecon.org/2012> > _______________________________________________ > cross-project-issues-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > > _______________________________________________ > cross-project-issues-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev _______________________________________________ cross-project-issues-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev _______________________________________________ cross-project-issues-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
