Authoring Tools memory consumption
Quote from JakeeeD on October 19, 2011, 11:22 amI have noticed that when using Authoring Tools, my system eventually warns me that my virtual memory is low and the system is going to increase the pagefile size. This is pretty annoying since when that happens, compilation tools are ignoring every command and I have to restart the system before I can compile anything.
I have decreased the number of undos, and my draw distance is set to very low. However the program is laggy, and starts eventually to become unresponsive. I don't know if it's some kind of memory leak, since the Portal 1 SDK works well and both games run smoothly.
The question is, what can I do to improve the performance of Authoring Tools?
I have noticed that when using Authoring Tools, my system eventually warns me that my virtual memory is low and the system is going to increase the pagefile size. This is pretty annoying since when that happens, compilation tools are ignoring every command and I have to restart the system before I can compile anything.
I have decreased the number of undos, and my draw distance is set to very low. However the program is laggy, and starts eventually to become unresponsive. I don't know if it's some kind of memory leak, since the Portal 1 SDK works well and both games run smoothly.
The question is, what can I do to improve the performance of Authoring Tools?
Quote from CaretCaret on October 19, 2011, 11:30 amBuy more RAM?
Buy more RAM?
"I hear voices. But I ignore them and I just carry on killing."
Quote from dinnesch on October 19, 2011, 11:53 amJudging from the warning you said you're getting, you run Windows XP? If yes, look here for a guide on how to increase your pagefile(virtual memory) size. If I guessed your OS wrongly, google is your friend
Compiling will take less resources if you lower quality - set RAD and VIS to fast, disable HDR.
Judging from the warning you said you're getting, you run Windows XP? If yes, look here for a guide on how to increase your pagefile(virtual memory) size. If I guessed your OS wrongly, google is your friend ![]()
Compiling will take less resources if you lower quality - set RAD and VIS to fast, disable HDR.
Quote from JakeeeD on October 19, 2011, 12:07 pmdinnesch wrote:Judging from the warning you said you're getting, you run Windows XP? If yes, look here for a guide on how to increase your pagefile(virtual memory) size. If I guessed your OS wrongly, google is your friend![]()
Compiling will take less resources if you lower quality - set RAD and VIS to fast, disable HDR.
I guess you got me wrong. I don't want to increase the pagefile (the size is now optimal) or buy more ram (DDR1 is so slow that it would be insane to buy it more than 1gb since Socket 939 isn't so fast that the processor could efficiently handle more than 1gb of it). I meant that if there's something that you can do software-side.
Also, compiling time isn't a problem, just that the system starts to ignore the memory commands after increasing pagefile size.
Compiling will take less resources if you lower quality - set RAD and VIS to fast, disable HDR.
I guess you got me wrong. I don't want to increase the pagefile (the size is now optimal) or buy more ram (DDR1 is so slow that it would be insane to buy it more than 1gb since Socket 939 isn't so fast that the processor could efficiently handle more than 1gb of it). I meant that if there's something that you can do software-side.
Also, compiling time isn't a problem, just that the system starts to ignore the memory commands after increasing pagefile size.
Quote from dinnesch on October 19, 2011, 12:25 pmJakeeeD wrote:I guess you got me wrong. I don't want to increase the pagefile (the size is now optimal) or buy more ram (DDR1 is so slow that it would be insane to buy it more than 1gb since Socket 939 isn't so fast that the processor could efficiently handle more than 1gb of it). I meant that if there's something that you can do software-side.Also, compiling time isn't a problem, just that the system starts to ignore the memory commands after increasing pagefile size.
Your pagefile size is clearly not optimal for running heavy programs like Hammer. If you get the 'increasing pagefile size' warning it means you exceeded your currently set amount, and Windows temporarily expands it to prevent a crash and that can greatly slow down your computer. Just set it higher(like 2-4GB), restart your computer and it will likely work better.
Of course a big pagefile is slower than a lot of RAM, but I think it's about the best improvement to make 'software-side' with only 1GB of RAM...
Also, compiling time isn't a problem, just that the system starts to ignore the memory commands after increasing pagefile size.
Your pagefile size is clearly not optimal for running heavy programs like Hammer. If you get the 'increasing pagefile size' warning it means you exceeded your currently set amount, and Windows temporarily expands it to prevent a crash and that can greatly slow down your computer. Just set it higher(like 2-4GB), restart your computer and it will likely work better.
Of course a big pagefile is slower than a lot of RAM, but I think it's about the best improvement to make 'software-side' with only 1GB of RAM...
Quote from JakeeeD on October 19, 2011, 1:15 pmThe pagefile is already 1,5gb, I'll consider increasing it. However I don't think that it will reduce lag.
It's strange, since technically the programs are pretty much the same (SDK Hammer and Portal 2 Hammer), and the SDK Hammer works just fine.
The pagefile is already 1,5gb, I'll consider increasing it. However I don't think that it will reduce lag.
It's strange, since technically the programs are pretty much the same (SDK Hammer and Portal 2 Hammer), and the SDK Hammer works just fine.
Quote from Robdon on October 19, 2011, 1:48 pmIs it certain maps or all of them that lag?
I recently upgraded from 3GB mem -> 6GB, and it made a big different using hammer.
It uses alot of memory, 1GB just for hammer, and then the compiling progs use lots also on top of that, depending on your map size and usage.
Rob.
Is it certain maps or all of them that lag?
I recently upgraded from 3GB mem -> 6GB, and it made a big different using hammer.
It uses alot of memory, 1GB just for hammer, and then the compiling progs use lots also on top of that, depending on your map size and usage.
Rob.
Quote from iWork925 on October 19, 2011, 5:05 pmI don't know how anyone would map with 1 gb of ram. I have 12gb and its still laggy as shit. If I was you I would buy ALOT more then 1 gb before I started mapping. Wait lemme guess... parent's computer? Tellem you need a better pc for school or something.
I don't know how anyone would map with 1 gb of ram. I have 12gb and its still laggy as shit. If I was you I would buy ALOT more then 1 gb before I started mapping. Wait lemme guess... parent's computer? Tellem you need a better pc for school or something.

PortalStories.com
"Oh, in case you got covered in that repulsion gel, here's some advice the lab boys gave me: DO NOT get covered in the repulsion gel."
Quote from JakeeeD on October 20, 2011, 3:16 amI was frustrated and increased the pagefile size to 3gb. Zoooooom.
No Hammer lag or long Portal 2 loading screens.
Thanks guys.
I was frustrated and increased the pagefile size to 3gb. Zoooooom.
No Hammer lag or long Portal 2 loading screens.
Thanks guys.
Quote from ChickenMobile on October 21, 2011, 1:12 amJakeeeD wrote:I was frustrated and increased the pagefile size to 3gb. Zoooooom.That took some time for you to change it xD. I think my page file takes around a 1/6 of my terrabyte drive.
Not like I need all of it though...
That took some time for you to change it xD. I think my page file takes around a 1/6 of my terrabyte drive. ![]()
Not like I need all of it though...

