Have to Restart (Computer Slow) Computer After Maxing Out Ram - Windows 7

creationsof12

Distinguished
Sep 11, 2011
65
1
18,635
We've got an interesting situation happening on all of our workstation machines:

Sometimes we will max out our ram and use 100% of the processing power through some of the software we use (normally during rendering in 3ds max or After Effects or even working on multiple massive Photoshop files) and of course, the computer acts a bit slow when it's maxed out like that. The strange part is that even after closing everything down and getting the ram back to a reasonable ~3GB, the computer will still act extremely sluggish until we restart the machine.

It's strange because we've taken some of these files home before, will max out the cpu + ram at home, bring the ram and cpu usage back down and the computer will run fine again. It's just on the workstation machines that a restart is required to get the system running smoothly again... and because we have so much software installed and startup software etc, it takes ages to restart.

The workstation machines are the Dell T7610's with 32GB of Ram, some of them with Quadro K2000's, K4000's, K5000's, etc.

Running Windows 7 Professional (64-bit)
Processors: 2x (hyperthreaded) Xeon E5-2620 v2 @ 2.10GHz
Hard drives: ATA WDC WD10EZEX-75M SCSI
RAM: DDR3 ECC 1866 8GB x4

I've been trying to figure this out for a a while now but... so far, no luck. I haven't been able to find much online about it either, which is making me think that it's just these machines.

Has anyone else out there been experiencing this issue? And if so, know of a solution? Any help would be greatly appreciated. I'm still working hard to narrow down the problem. Any suggestions are more than welcome!

If there is even a solution to clearing memory in some way that would prevent us from having to restart the machines each time, that would be perfect. Though I'm not sure that that is where the problem is coming from.
 
Solution
creationsof12,

My first idea is that the system (Precision T7610 @X E5-2620 v2 6-core @ 2.1 / 2.6GHz) is bottlenecking, by a combination of the low clock speed of the E5-2620 v2 and disk performance at the CPU to RAM to disk swaps. the idea that dual 6-core CPU's are running a 100% seems to a sign of lack of processing power. These two factors though may be separated and to evaluate changes, concentrate first on the disk performance.

In 3ds Max especially, the number of calculations to generate polygons position, especially when using heavy textures, or particles- reflections, liquids, etc. will pile up in the thread distribution and swaps to RAM which becomes saturated. The reason it speeds up after a restart is that the RAM has been flushed during the restart. If 3ds is also accessing for example textures libraries on the HD, the situation becomes worse.

On Passmark Performance Test baselines, an Advanced Search: "T7610, E5-2620 v2 , K" -which will filter GPU's beginning with a K, lists 6 systems of which 3 systems are using 2X E5-2620 v2. These systems as GPU have: Quadro K5000, K4200, and K5000.

The relevant results are the CPU and Disk scores:

CPU: 13482, 13152, 12009
DIsk: 7246 (LSI Logical Volume), 3746 (Liteonit LCS256), 3639 (Intel SSDSC28848)

An Advanced Search: : E5-2620 v2, WD10EZEX lists 11 systems, 6 of which are using 2X E5-2620 v2:

CPU: 14817, 14811, 14793, 14516, 14167
Disk: 2180 (this must be a RAID 0), 1139, 1093, 1182, 1059, 979

The CPU scores are reflective of the number of calculation cycle and as that rating is distributed over tall the threads, the rating appears adequate. However, the 2.7GHz maximum clock speed produces a single-threaded performance rating of only 1269. Compare this to the 1271 single-threaded performance rating of a Core2 Quad Q9650, which is a non-hyperthreading 3.0GHz CPU released in the 3rd quarter of 2008. If I might say it in these terms, the Xeon E5-2620 v2 is an excellent moderate load server processor, but nominal in rendering requiring careful thread allocation, and sub-nomimal for professional 3ds use.

As well, the disks scores quoted are in my view, substandard to the demands of 3D modeling and rendering.

My suggestion is to first, run the Passmark Performance Test and compare your CPU and Disk results to the above.

My expectation is that the CPU performance is nominally adequate and the problem is the disk performance. The Western Digital Blue is very good for a mechanical drive, but well below that necessary for 3D modeling.

Suggested Sequence:

1. Test with Passmark
2. If the test results have a CPU mark much below 12000:
___ A. check in BIOS that Hyperthreading is enabled
___ B. check in Control Panel > Power Options that the power plan is set to "High Performance"
3. If the CPU scores are in the 13000+ range, buy and install as a test a Samsung 850 Evo 250GB (about $90)
4. Start the identical rendering on the SSD upgraded and an original WD10EZEX T7610 and time the results.
4A. Test navigation and alterations to a 3ds model.
5. If the SSD- equipped system is performing adequately, supply all the systems with that drive.
6. If performance is inadequate, buy a pair of used Xeon E5-2680 CPU's (8-core @ 2.7 / 3.5GHz) (Approx $200 each):
____ http://ark.intel.com/products/64583/Intel-Xeon-Processor-E5-2680-20M-Cache-2_70-GHz-8_00-GTs-Intel-QPI
7 Install and test in the SSD- equipped system.
8. If the performance is adequate- consider changing the CPU's to used E5-2680's.

In any event, if you like, run the Passmark Test and post the results in this thread and it may well reveal the situation.

Here's hoping it's only a setting, but my intuition is the system is crying out for a fast SSD. The E5-2680 should significantly speed up modeling also as they would run at 3.5GHz instead of 2.6GHz. the single-threaded performance of the E5-2620 v2 is 1269, while the single-threaded score for the E5-2680 is 1709, or +34%. Importantly, the change is increasing the number of threads that may be assigned to rendering from 24 per system to 32 at +600MHz (that is from 2.1GHz to 2.7Ghz). Depending on your firm's billing rate, the CPU change could pay for itself in a few days' time. Check however, for implications as to the system warranty and make a risk assessment.

Cheers,

BambiBoom

Modeling:

1. HP z420 (2015) > Xeon E5-1660 v2 (6-core @ 3.7 / 4.0GHz) > 32GB DDR3 1866 ECC RAM > Quadro K4200 (4GB) > Intel 730 480GB (9SSDSC2BP480G4R5) > Western Digital Black WD1003FZEX 1TB> M-Audio 192 sound card > 600W PSU> > Windows 7 Professional 64-bit > Logitech z2300 speakers > 2X Dell Ultrasharp U2715H (2560 X 1440)>
[ Passmark Rating = 5064 > CPU= 13989 / 2D= 819 / 3D= 4596 / Mem= 2772 / Disk= 4555]
[Cinebench R15 > CPU = 1014 OpenGL= 126.59 FPS] 7.8.15

Pending upgrade: HP /LSI 9212-4i PCIe SAS /SATA HBA RAID controller, 2X Seagate Constellation ES.3 1TB (RAID 1)

Rendering:

2. Dell Precision T5500 (2011) (Revised) > 2X Xeon X5680 (6 -core @ 3.33 / 3.6GHz), 48GB DDR3 1333 ECC Reg. > Quadro K2200 (4GB ) > PERC H310 / Samsung 840 250GB / WD RE4 Enterprise 1TB > M-Audio 192 sound card > 875W PSU > Windows 7 Professional 64> HP 2711x (27", 1920 X 1080)
[ Passmark system rating = 3844 / CPU = 15047 / 2D= 662 / 3D= 3500 / Mem= 1785 / Disk= 2649] (12.30.15)


 

creationsof12

Distinguished
Sep 11, 2011
65
1
18,635


Sorry, I should have clarified: At normal use (in most of the software we use), the CPU usage is around 5%. It only goes to 100% upon rendering. But the slow down will still occur even when the processing power is down to around 5% but the ram maxes out. Which, yeah, makes me think it has something to do with the CPU to RAM to disk swaps (as you mentioned).

What I was wondering about, I guess, is if there was another way to "flush the RAM" without having to restart the computer. The computers run fine (even with the slower Xeon processors and hard drive) in normal use. We only get the problem after maxing out the RAM. After maxing it out, the computer will remain sluggish even after closing out of all software. Even opening an explorer window after that will take about 30 seconds. Opening some of the larger software like 3ds max, After Effects, etc. will take up to 15 minutes.

It doesn't seem to matter what software we use to max out the ram, which tells me it's not a software issue (in terms of Max, AE, etc). We pull textures from our server and have >Gigabit setup for the network. Things would definitely go faster for us if we had SSD's or more powerful processors but that doesn't seem to be an option for us right now. I'll still run the tests as you suggest and just see what kind of scores we get.

But yeah, I really think it's something to do with the way it's handling the physical and virtual memory. Could be wrong though. I'll go through and try each of your suggestions and post what I find. I'll have to see about testing things like an SSD or more powerful processors though.

Thanks for your response and suggestions! REALLY appreciate it!
 



creations of 12,

It occurred to me that the problem may gave to do with virtual memory and Pagefile, especially if the files are large. If the RAM is saturated, a problem that might arise as the Pagefile will be 32GB- the same size as the RAM, but is kept on an HD which is too slow to act efficiently as virtual memory- in which case that's the RAM /disk swap bottleneck. So, the answer may actually to increase the RAM, perhaps to 64GB. On my dual 6-core rendering system (Dell Precision T5500) I have 48GB but my files are not very large and the SSD is reasonably fast.

1. Check if Pagefile (virtual memory) is disabled and check the volume settings.
2. Try changing the Pagefile to 64GB.
2. If results are not satisfactory, test this idea by temporarily transferring the RAM from one system to the test system so as to test with 64GB physical memory.

It's possible to create a desktop icon that clears memory cache. See:

"Clear Memory Cache on Windows 7"

http://medicine.arizona.edu/helpdesk-article/clear-memory-cache-windows-7

Cheers,

BambiBoom


 
Solution

creationsof12

Distinguished
Sep 11, 2011
65
1
18,635


The "Clear Memory Cache on Windows 7" shortcut seems to solve the problem! As soon as I ran it, the machine sped up instantly and was back to normal. I've done a few tests now, seems to work every time. The amount of RAM being used actually barely moves (maybe a couple hundred megabytes) so I assume that it cleared cache that was on the hard disk(?).

Anyway: A thousand thank you's, BambiBoom!