× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Joe Pluta skrev den 26-02-2008 17:51:

Okay, but I think it's silly. I have a machine that regularly runs WDSC *and* RBD *and* open office *and* thunderbird *and* firefox *and* iseries navigator *and* putty *and* iseries access.

Right now, in fact, I've got all those applications up, and while they have admittedly small projects, my current memory commitment is 1.3GB. Everything flies, and it's an incredible working environment. Also, the entire machine (including a 3GHz dual core processor, 3GB of RAM, and a 160GB 10K SATA drive) cost about $800, with Windows XP installed.

What you think is silly may make perfect sense for others.
Some coorporate environments - like mine - may enforce the usage of anti-virus programs, which is non-negotiable. This makes a severe impact on the disk system, and means that you basically want to have as much memory for disk caching as you possibly can. On top of that we are migrating to laptops, which have slower harddisks.
I have a dual core Intel chip and 2 Gb of RAM and my WSDCi takes in the order of minutes to cold start. Fortunately warm starting is much faster.

Now, if you're running virtual machines on your workstation, then you have memory issues. But really, you should be running VMs on a box dedicated to the VMs. That one may require a 64-bit OS to be able to run massive amounts of memory, but you wouldn't be running WDSC or RDi on that machine (typically).
Our requirements are different. Production VM's should run on a production server but for testing and development nothing beats having everything with you. It also takes network issues out of the equation, which may be crucial when at other locations.

However, I am pretty certain that the basic problem with WSDCi is that it uses native code instead of pure Java. Otherwise it would be rather simple to migrate to any platform supported by Eclipse.

It will be interesting to see if the new version will depend on JTOpen only, as that would most likely fix this problem area.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.