Thursday, April 10, 2008

Connection manager ของ openfire

Me and Tae can setup "Connection manager" to connect to openfire one step completed.
As it, We still cannot setup http-bind to work in Connection manager. however, It's not depend on load test with jabsimul (./jab_simule) which noneed of http-bind.

So I need to post latest result of this testing.

Openfire server is install in 2 Core 2 Duo CPU Xeon 2.8GHz and 2GB Ram..
which assigned Java VM memory maximum is 1 GB

Connection manager installed in same server and assigned memory 1 GB to it.. so CM is very load this server

My 2 Computer, 1 PC Desktop run Fedora Core8 in VMWare 2GB Ram and 1 Notebook Toshiba Core2 Duo 1.8GHz 1.5 GB Ram. They can simulate 35,000(36,000) concurrent user which do event signin and send message every minutes...

I have to seperate jabsimule to run only 2,000 concurrent user in each terminal instant because I have found that if you run more than 4000 user, jabsumul will fail with error "segmentation fault" which i don't know what it is.

So, My notebook can run only 12 instant of jab_simul and then it have very slow action in windows.. 6 instant can run on PC and work properly

In case you would like to use CM in same server , you need to configure 5222 port of openfire to be not confilc with CM listen port (5222 to) you can change it in CM or change listen port on Openfire .. To test with jab_simule you need to change openfire listen port..

Without CM, 1 GB of openfire can support 35,000 completly and No delay !!

But with Connection manager, openfire can support 35,000 too but it have more delay times.. I test it by try connecting to openfire with PSI and chat between user..

So.. I forget to tell about CM setting

1.In case install it in same server, You need to change port at server>Edit properties (Button)
Tae and I changed "Client Port:" and "Client SSL Port: " to other port and let 5222 to listen by CM.

2. You have to setup password for CM to connect to openfire in tab in the left "Server setting">"connection manager"
Chnage to enable it and fill the password in and save

3. Go to CM directory by terminal, then go to ./conf/manager.xml set this field as below

- domain
- port
- password
- connections , if you have more than one CM you should change this field as id number of CM

- socket - default port 5222 => you should let it be the same
- ssl - as defalut port too

4. then to run it and assign java memory, you can config run script in ./bin or directly call java -jar as below

java -Xms512m -Xmx768m -jar ../lib/startup.jar

hope it useful for someone...

No comments: