WSAD4 around developing large applications is considerably slower than VAJ. WSAD4 have also noticed the tools' poor performance when debugging. Do you have any comments/suggestions on this issue?
Hi, I just came from a WebSphere users group meeting, and IBM is suggesting that you have at least 500MB of RAM for this application, and 1GB makes your life easier. Why it takes so much, I don't know. But during their presentation, the guy kept getting "Low virtual memory" on his laptop and eventually had to reboot. I personally have never used this tool. I'm just reporting what I was told and what I saw. Kind of scary. Barry
Amy Howard
Ranch Hand
Joined: Jul 11, 2002
Posts: 86
posted
0
We may, however, already be maxed out at 512M on our current machines.
garth schneider
Ranch Hand
Joined: Mar 20, 2002
Posts: 95
posted
0
I remember when I started working with VAJ with 128 of ram. It really was slow then. I went to 256 and life was pretty good. I have been working with WSAD 4.0 and now WSAD 5.0 and 512 is not enough anymore. You really need a Gig. My memory usage in debugging is getting to around 860 mb. If you have the memory things go pretty good now. You have to remember that WSAD is doing a lot more for you as well. What use to take VAJ and WebSphere Studio Classic running at the same time is now all included in WSAD. WSAD 5.0 is a great environment. Garth SCJP IBM Solution Developer for VAJ and WSAD 4.0 IBM Object Oriented Analysis and Design with UML.
0
