![]() ![]() ![]() ![]() So this paging and swapping drastically slows the rendering process.įor these 32-bit Windows versions, more than 2GB of RAM memory probably isn't cost-effective. Eventually, the rendering will complete, but disk drive access is said to be 1000 times slower than RAM access. Windows must swap parts of your program and data to disk. ![]() If during a rendering the CommitCharge/Total is way above the PhysicalMemory/Total (say 50% higher, or double), Rhino and Flamingo are demanding more virtual memory space than your RAM. Then look down in the lower left corner at Commit Charge (total memory space currently used by Windows for everything, including Rhino and Flamingo). On the Performance tab, note the PhysicalMemory/Total (your amount of RAM). More RAM speeds up rendering.įor more precision about RAM on NT, Win2000, XP, or Vista, run Task Manager. If the rendering process causes a significant amount of disk accesses (paging, swapping) Flamingo slows down. You should see very little disk activity (unless some other application is working hard). Watch your disk drive light while the image is painting on the screen. To recognize a RAM shortage, watch disk accesses, or use Task Manager, as below. Rendering with inadequate RAM memory is a major reason for slow Flamingo performance. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |