Icon View Thread

The following is the text of the current message along with any replies.
Messages 11 to 15 of 15 total
Thread Delphi 2006 - Trying Again - Slow Slow Slow
Fri, Apr 7 2006 11:59 AMPermanent Link

Jon Lloyd Duerdoth
I love my 1600 x 1200.

Roy:  How much memory do you have?  I'm running with 1G
      but wonder if there's any merit in adding another G.

      Yes, I know that more is always better... but wondered if
      the difference would be worthwhile.

Jon

Roy Lambert wrote:
> Sean
>
>> Why go to borland.public.delphi.ide.general? I've got you
>> here to distill it all in a quick post Smile
>
> Because there's lots of stuff there, and if the red squiggles hadn't annoyed me I wouldn't have done anything about it and wouldn't have been able to tell you <vbcg>. Plus there's other stuff - definitely worth wading through.
>
>> I still don't like the way D2006 takes up more screen real
>> estate, so I'm pushing the boss for a nice 24" monitor to
>> help me take the big plunge.
>
> Go for a wide screen monitor - I'm using an HP zd8000 and its great.
>
> Roy Lambert
Fri, Apr 7 2006 1:30 PMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Jon

>I love my 1600 x 1200.

Showoff - mines 1440 x 900

>
>Roy: How much memory do you have? I'm running with 1G
> but wonder if there's any merit in adding another G.
>
> Yes, I know that more is always better... but wondered if
> the difference would be worthwhile.


There you go - another good reason to join the Borland ng.

I upgraded to 1Gb  Not sure if more would help and I can't remember anything definitive from the ng. I do remember posts about a major memory leak in the IDE (300Mb+ after a couple of hours) but I haven't noticed that yet.

Personally if I wasn't getting moch disk swaping I'd leave it alone.

Roy Lambert
Fri, Apr 7 2006 4:04 PMPermanent Link

Jon Lloyd Duerdoth
I had wondered about a memory leak as the time it slowed down
(even after the Error Insight fix) occurred after lots of recompiles
etc.

I think I did a reboot and got all the memory back.

Jon

Roy Lambert wrote:
> Jon
>
>> I love my 1600 x 1200.
>
> Showoff - mines 1440 x 900
>
>> Roy: How much memory do you have? I'm running with 1G
>> but wonder if there's any merit in adding another G.
>>
>> Yes, I know that more is always better... but wondered if
>> the difference would be worthwhile.
>
>
> There you go - another good reason to join the Borland ng.
>
> I upgraded to 1Gb  Not sure if more would help and I can't remember anything definitive from the ng. I do remember posts about a major memory leak in the IDE (300Mb+ after a couple of hours) but I haven't noticed that yet.
>
> Personally if I wasn't getting moch disk swaping I'd leave it alone.
>
> Roy Lambert
Sat, Apr 8 2006 10:55 PMPermanent Link

Jon Lloyd Duerdoth
Found another setting that helps

Click the "Set Debug Desktop" icon (found probably at extreme right)
and select "None"

Saves the delay when the test run finishes and it redraws the screen.

Jon

Jon Lloyd Duerdoth wrote:
> I had wondered about a memory leak as the time it slowed down
> (even after the Error Insight fix) occurred after lots of recompiles
> etc.
>
> I think I did a reboot and got all the memory back.
>
> Jon
>
> Roy Lambert wrote:
>> Jon
>>
>>> I love my 1600 x 1200.
>>
>> Showoff - mines 1440 x 900
>>
>>> Roy: How much memory do you have? I'm running with 1G
>>> but wonder if there's any merit in adding another G.
>>>
>>> Yes, I know that more is always better... but wondered if
>>> the difference would be worthwhile.
>>
>>
>> There you go - another good reason to join the Borland ng.
>>
>> I upgraded to 1Gb  Not sure if more would help and I can't remember
>> anything definitive from the ng. I do remember posts about a major
>> memory leak in the IDE (300Mb+ after a couple of hours) but I haven't
>> noticed that yet.
>>
>> Personally if I wasn't getting moch disk swaping I'd leave it alone.
>>
>> Roy Lambert
Sun, Apr 9 2006 2:19 AMPermanent Link

Dave M
Sean McCall <NoSpam@nowhere.com> wrote:

>I decided to give D2006 a try again. For the first time I
>actually got some D6 component code to compile & so moved on
>to typing in some new code. Its like typing on a circa 1981
>computer terminal using an acoustic coupler... the character
>display is almost a second behind the keyboard  & the CPU
>usage jumps to 100%. Anyone had this problem or know the cure?

There is a recommendation to uncheck "Show Palette Wizards" and if I remember correctly,
check "Always Show Designer Items."
May have come from Alan Bauer...

I had *bad* slow downs using the embedded designer with form inheritance.  So I use the
floating designer.

Also, you need about 1 gig ram for professional.

Dave M
« Previous PagePage 2 of 2
Jump to Page:  1 2
Image