[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[cross-project-issues-dev] Fw: Hudson sluggishness
|
Resending.. (appears my earlier attempt got rejected)
Hello all,
I just joined this mailing list!
I would recommend to move to Hudson 2.2.0. The main reason for switching
to Hudson 2.2.0 is support for project cascading [1] [2]. However,
Hudson 2.2.0 changes project structure, so we need to be careful about
backing up the home directory before switching, in case Hudson 2.2.0
doesn't live up to the expectation.
I don't think Hudson 2.2.0 would solve the sluggishness problem.
Sluggishness is not mainly due to Hudson Application, it also depends on
the Servlet containers ability to scale. I'm working with Matt and
looking in to possible ways to improve the response. I will write a
detail message on that.
Also, as mentioned by Matt, please do not use hudson context URL to
download huge directories. We should keep hudson application purely for
building and viewing status and results. Downloading few artifacts is
ok. We could have solutions some thing like
- By pass hudson servlet and create a sub context in Apache (Hudson is
proxied by Apache) that points to the workspaces, so download happens
via Apache not Hudson Servlet.
- Use post build action in your job to push (publish) your project
artifacts to location of your choice. I think SCP plugin may be useful.
I'm also analyzing the heap dump (2 GB!!), using Eclipse Memory
Analyzer, to find out memory leaks which is killing Hudson slowly.
Hudson 3.0.0 is not ready (not even close ). Due IP cleaning, it is
going though huge changes, mainly due to external library dependencies.
We don't expect it to be ready before June-July time frame.
[1] http://wiki.hudson-ci.org/display/HUDSON/Project+cascading
[2]
http://hudsoncentral.wordpress.com/2011/10/28/cascading-projects-released-as-beta/
(it's no longer BETA though)
- Winston
