AJDT is slow [message #591666] |
Tue, 10 January 2006 11:11 |
Konstantin Scheglov Messages: 555 Registered: July 2009 |
Senior Member |
|
|
I have several performance related questions.
1. What is AJDE and why is it so slow? See log log from "AJDT Event
Trace" below.
2. Is it true, that if I have one project (p1) with aspects (and classes
that should be processed) and other project (p2) that _uses_ processed
classes, then p2 should be also AJDT project? I know, that I don't need
"around", only "before" and "after".
3. Damn, in p1 I have _one_ aspect and _two_ beans that should be
processed. And right now it takes almost _6_ seconds to compile such
trivial case?! I use 256 Mb for Eclipse, so I think that memory is not
problem.
No, I am not negative, I like AJDT a lot, it is convinient, but so
slow... :-(
--------
13:51:35
============================================================ ===============================
13:51:35 Build kind = AUTOBUILD
13:51:35 Project=ru.nlmk.lab.admin.ui kind of build requested
=Incremental AspectJ compilation
13:51:35 build: Examined delta - source file changes in required
project ru.nlmk.lab.admin.ui
13:51:41 Timer event: 5689ms: Time to first compiled message
13:51:41 Timer event: 5699ms: Time to first woven message
13:51:41 AspectJ reports build successful, build was: INCREMENTAL
13:51:41 Timer event: 5779ms: Total time spent in AJDE
13:51:41 Timer event: 20ms: Create element map (0 rels in project:
ru.nlmk.lab.admin.ui)
13:51:41 Types affected during build = 1
13:51:41 Timer event: 0ms: Add markers (0 markers)
13:51:41 Timer event: 5959ms: Total time spent in AJBuilder.build()
--------
--
SY, Konstantin.
Advanced Eclipse SWT Designer (http://www.swt-designer.com)
Konstantin Scheglov,
Google, Inc.
|
|
|
Powered by
FUDForum. Page generated in 0.03063 seconds