Thread View: borland.public.jbuilder.java.api
3 messages
3 total messages
Started by KLT
Wed, 20 Oct 2004 16:14
JBuilderX is using killing my processor
Author: KLT
Date: Wed, 20 Oct 2004 16:14
Date: Wed, 20 Oct 2004 16:14
3 lines
1081 bytes
1081 bytes
General Question... I have just installed jbuilderX developer (upgrade from jbuilder4, yea I'm old), and my processor is getting hammered, and I'm just sitting in the API. Does anyone happen to know what new "feature" is running in the background to beat up the processor so much? Thanks in advance for any suggestions. /klt
Re: JBuilderX is using killing my processor
Author: Paul Furbacher [TeamB]
Date: Wed, 20 Oct 2004 21:38
Date: Wed, 20 Oct 2004 21:38
35 lines
2150 bytes
2150 bytes
KLT wrote:
> General Question... I have just installed jbuilderX developer
> (upgrade from jbuilder4, yea I'm old), and my processor is getting
> hammered, and I'm just sitting in the API. Does anyone happen to
> know what new "feature" is running in the background to beat up the
> processor so much? Thanks in advance for any suggestions. /klt
First, does your machine meet the minimum
system requirements for JBuilder X?
I think you can find those requirements
in the release notes ... in the "setup"
directory.
If your system is up-to-snuff, have you adjusted
the memory settings in the bin/jbuilder.config
file? Try something like 392 mb, instead of the
default (128, or 256 mb ... cannot remember what
it was).
--
Paul Furbacher (TeamB)
Save time, search the archives:
http://www.borland.com/newsgroups/ngsearch.html
Is it in Joi Ellis's Faq-O-Matic?
http://www.visi.com/~gyles19/fom-serve/cache/1.html
Finally, please send responses to the newsgroup only.
That means, do not send email directly to me.
Thank you.
Re: JBuilderX is using killing my processor
Author: Keith Thompson
Date: Thu, 21 Oct 2004 18:30
Date: Thu, 21 Oct 2004 18:30
48 lines
2943 bytes
2943 bytes
Found it... It is related to the Project View. When I startup JBuilder and have the projectView window open, it scans indefinitely. If I "pin" the window to the left part of the screen (or close the view completly), then the processor drops to a normal level. After I close or pin that view the first time, the rest of the time it functions properly. I personally prefer to have it "pinned", so thats my default, and life is good again! Thanks for your response, my system is barely up to "snuff", so I'll remember the jbuilder.conf file for future reference. "Paul Furbacher [TeamB]" <pfurbacher@mac.com> wrote in message news:4176daf4$1@newsgroups.borland.com... > KLT wrote: > > > General Question... I have just installed jbuilderX developer > > (upgrade from jbuilder4, yea I'm old), and my processor is getting > > hammered, and I'm just sitting in the API. Does anyone happen to > > know what new "feature" is running in the background to beat up the > > processor so much? Thanks in advance for any suggestions. /klt > > First, does your machine meet the minimum > system requirements for JBuilder X? > I think you can find those requirements > in the release notes ... in the "setup" > directory. > > If your system is up-to-snuff, have you adjusted > the memory settings in the bin/jbuilder.config > file? Try something like 392 mb, instead of the > default (128, or 256 mb ... cannot remember what > it was). > > > -- > > > Paul Furbacher (TeamB) > > Save time, search the archives: > http://www.borland.com/newsgroups/ngsearch.html > > Is it in Joi Ellis's Faq-O-Matic? > http://www.visi.com/~gyles19/fom-serve/cache/1.html > > Finally, please send responses to the newsgroup only. > That means, do not send email directly to me. > Thank you.
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads