|Slow publishing in Linux? [message #212261]
||Thu, 10 April 2008 21:42
Originally posted by: simensen.gmail.com|
I have a project that is extremely slow to publish in Eclipse when run
under Linux. This same project publishes much more quickly when published
using a Windows Eclipse.
What is the best way to debug what is actually going on? The details for
Progress just show it saying, "Copying from text-base to text base" and
gets stuck there for awhile. I see it switching to other folders from time
to time, but it happens much more slowly than I would expect (I'm talking
at least 5 minutes-- I've yet had the patience to wait for it to actually
I am mostly positive that it is not the disk that is the issue. I can copy
the entire project ( including the target/ folders ) faster than I can
publish just one of the projects to Tomcat.
I moved to Linux because I could see that compiling from the command line
was way faster on Linux than on Windows. I assumed that Eclipse
performance would be close or better under Linux. For cleaning and
building the project, this looks to be true. However, this slow publishing
issue will definitely be a show stopper.
|Re: Slow publishing in Linux? [message #212295 is a reply to message #212281]
||Fri, 11 April 2008 11:26
| Larry Isaacs
Registered: July 2009
Beau D. Simensen wrote:|
> It looks like this might be related to choosing "Use Tomcat installation
> (takes control of Tomcat installation)" instead of "Use workspace
> metadata (does not modify Tomcat installation)" -- is there any reason
> there might be a difference here?
There is a difference. With "Use Tomcat installation...", publishing
assumes that external changes could have been made to the webapp copy in
the installation and attempts to synchronize that webapp with the
project. This means all files get checked to see if dates match and
those that don't match get copied. Any extra files found in the
installed webapp not also in the project are deleted. Finally, there is
a bug related to "Use Tomcat installation...", now fixed in WTP 3.0,
that causes utility projects to rebuild their jar on every publish.
For the "non-Use Tomcat installation" options, only files that changed
since the last publish (determined from some cached data) are copied to
the webapp. Also, Bug 211660 doesn't apply, so utility projects are
rebuilt only if something changed. Since WTP assumes it "owns" that
Tomcat instance, this simpler form of publishing is considered sufficient.
Powered by FUDForum
. Page generated in 0.01455 seconds