Making TD run faster

  • Thread starter Thread starter David D
  • Start date Start date
D

David D

I just upgraded the PC I use for TD.
Loading, saving, Dependancy checking as well as builds still take quite a
while to run.
I am running the system from the same PC I have the database installed onto.
Increasing from 512MB to 1Gig RAM had no affect.
Any idea on what features of the PC determines build speed?
Celeron vs Pentium?
HD speed?
Raw CPU Mhz?
Any tweeks that can be done?
 
For grins, go to taskmanager and check your CPU Utilization. It's probably
pegged at 100%
If so, then you have the same experience I and others have had on certain
machines. I have not found a fix yet.
 
Couple of small suggestions...

1. Try re-installing the tools after you have the 1GB RAM installed. I have
seen issues with MSDE and RAM upgrades...

2. Obviously a Multi-Processor PC is always good. :-) Something along the
lines of a Quad Xeon :-) HAHA. Actually even a HT P4 helps a little. Cache
on Die is another big one. The P4 Extreme is quite nice (I sound like an
Intel commercial)

3. Striped drives are nice. Especially SATA or SCSI... PATA is marginal with
striping.

4. Another thing that helps is spreading your swap file across 2 Physical
volumes.

HTH,
JC
 
Hi,

1 GB is barely ok for caching minlogon projects. If you want to have everything cached in memory then 4GB+ would be nice. (2GB might
help)
In case of huge memory only first build take time since files need to be loaded in SQL cache and all rest of memory is used by OS to
cache all files that are read from disk. So all successive request go to memory instead of disk.
So with this scenario swap file is not an issue here that will improve performance.
Also striped drives are nice. But they significance is greatly reduced with enough memory.

Regards,
Slobodan
 
Talking about SQL Server 2000... You can tune much things there for better performance.

If you really need pagefile (while having much RAM installed) consider tweaking sql server working set size.

Also, tweaking minimum memory query option can help you to improve TD Filter options.

Speaking about 100% CPU utilization.. Look at the SQL Server recovery interval.

Some more info here: http://www.mssqlcity.com/Tips/tipSrvSet.htm

KM
 
Hi David,

some info that can show you how slow TD could be:

All tests with remote DB (SQL2000 on a quite powerful machine), 100MB
Ethernet, project with ~1500 components.

P4-2.8GHz / 512RAM Athlon-1.3GHz / 768RAM
Project load 4:45 6:56
Depend. check 0:56 1:32
Project upgrade 1:40 2:50
Project build 15:18 24:13
TD close 0:57 0:58

So, M$ did a lot efforts to support chip makers.

I guess P4-3.0 with HT / 1GB RAM / fast hdd and keeping SQL on the same
machine would make TD speed some how acceptable.
 
Back
Top