FYI: Java is a hog! 2

[atcom]

I can't believe how long OneX takes to start on the UCM, thanks Java

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
9365 onexp 20 0 1145m 585m 14m S 129.9 29.1 8:57.86 java


-----------------------------------

Calgary Telephone Systems, Avaya LG Asterisk (FreePBX) VOIP & TDM

 

[derfloh]

And how it can use 129% of CPU power...

 

[kyle555]

I don't think "top" is accurate with regards to Java virtual machines. Java does "hog" all it can, but will still release cpu cycles and ram to the OS if requested and it isn't using it.

http://stackoverflow.com/questions/...ge-from-java-under-linux-too-much-memory-used

Some guy made "Hello World" use 4 gigs of RAM according to the underlying OS. It doesn't mean it's "real

 

[atcom]

Well it takes long enough! I'm guessing the 129% is 129/200 due to the two cores...

-----------------------------------

Calgary Telephone Systems, Avaya LG Asterisk (FreePBX) VOIP & TDM

 

[kyle555]

I've heard 15 minutes exactly on the nose for Portal to start on some systems. In a VMWare one I manage, it is precisely 3 minutes.

Probably a bunch of steps that "wait 10 seconds" and check after in a way that it always takes the exact same long amount of time.

 

[sizbut]

Turn of the one-x portal logging. It dramatically reduces the portal restart time (assuming of course you don't need the logging on during restart to spot some issue).

Stuck in a never ending cycle of file copying.

 

[tlpeter]

The logs are a joke anyway.
So much information and a reinstall is mostly the quickest anyway.
I turn them off as it uses disk space like it is for free.

BAZINGA!

I'm not insane, my mother had me tested!

 

[intrigrant]

It isn't JRE which starts slow, it are the apps slowing it down...
When building software there are several compiler options to set, like optimize execution speed or optimize code size etc.
Then when building code the programmer must realize which functions are optimum in speed or code size.
A loop can be done in several ways:
- for x = 1 to 1000 step 1

code​

next x
- while x <= 1000 then

code​

wend
and there are more constuctions, the first one gives the smallest code but execution is way slower as example 2 which generates more code.

ergo: it is the software engineers to blame if sofware is slow not the used OS/VM

 

[holdmusic34]

Deleted 40GB of logs today off a customer's VMPro server. VMPro has no space to record. Check the folder.150 Mb of recordings.
Played the right click>properties game with the C drive.

OneX was writing logs that were hundred's of megs deep. Didn't even know the customer had One x. They don't even use it!

Are you a designated survivor, or holder of the cheget kind of guy?