Sunday, August 01, 2010

My development box

The kit:
Intel i7 860 (A decent quad core, 64 bit, 8 thread processor)
6 GB Memory
Windows 7 (64 bit)
A 64 bit JDK (with a 32 bit JDK installed as backup just for JDeveloper at design time at the moment)


Running a weblogic cluster  with 2 managed SOA servers (Oracle SOA suite 11.1.1).
A weblogic admin server.
Making do with an XE database for now, the full blown Enterprise 11gR2 database - maybe later on a need basis. 


With the above running, i've already hit 5.17G of memory usage.
Another half a gig should do for JDeveloper.


But with a node manager and a BAM server, it should soon be time to stack in a set of low latency RAM cards - 8G to keep the sanity of a 'development box'; 16G be the dream.


Before that, I could do with switching off the Aero theme and other bells and whistles.
Disk transfer rate on this box is not on my side here, so i'm really not keen on anything crucial swapping in and out. So far, I haven't heard


Bottleneck:
- Not the fastest disk I/O
- Not the lowest latency RAM either; could do with a faster 8G of RAM.


Gotchas!:
1. All weblogic servers are running with the 64 bit JDK. However, the first time I attempted to start the managed servers, it went into a FORCED shutdown as soon as I entered the username  via commandline. No stacktraces could be saved for future examination. 
However, setting up boot.properties got me past this.


2. Nodemanager still coughs up this nasty error 
but so far, this setup is on a dream run.. 




Update: 2/Aug/10
Running steady at about 4.1G Physical memory. 


Update: 3/Aug/10
All servers running steady. Used in full throttle, memory usage peaked at 5.18G. 
Left undisturbed (with JDeveloper open) it steadied at 4G. 
Woke the machine from sleep (with everything still running) and the memory usage rose from ~2.7G. 


Nothing cataclysmic attempted yet except for a separate OSB server and now i've hit 5.77G
(default Xmx values so far)

No comments: