Just thought it would be usefull to remind all that.
Each time you are modifying original files you are losing upgrade capabilities. Live Helper Chat is very flexible and allows to change almoust everything without changing kernel.
If you have any question use google group or just leave a comment :)
Just pushed small update on github master branch which fixes some stability issues then user or operator is typing very fast and sending messages. There was posibility of duplicates messsages. So no more duplicate messages it should be rock solid now. So as promised - I will fix every bug as fast as I can and ofcourse I can reproduce.
Don't foget to give g+ or rate this app in hotscripts or make small donation. If anyone will notice any other issues let me know :)
This time new features related release:
Feel free to report any issues. Demo also was updated. So we are going to kill all commercial projects peace by peace and make one of the best Live Support available for free.
I thought it would be interesting to see some performance testing. This time we simulate 1000 request with 5 concurent connections.
[demo]# ab -c 5 -n 1000 http://demo.livehelperchat.com/index.php/chat/syncuser/6/22/1e16f65d63f270401f90082a6fac9f3200ddab5d
This is ApacheBench, Version 2.3 <$Revision: 655654 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/
Benchmarking demo.livehelperchat.com (be patient)
Completed 100 requests
Completed 200 requests
Completed 300 requests
Completed 400 requests
Completed 500 requests
Completed 600 requests
Completed 700 requests
Completed 800 requests
Completed 900 requests
Completed 1000 requests
Finished 1000 requests
Server Software: nginx
Server Hostname: demo.livehelperchat.com
Server Port: 80
Document Path: /index.php/chat/syncuser/6/22/1e16f65d63f270401f90082a6fac9f3200ddab5d
Document Length: 103 bytes
Concurrency Level: 5
Time taken for tests: 5.349 seconds
Complete requests: 1000
Failed requests: 0
Write errors: 0
Total transferred: 462000 bytes
HTML transferred: 103000 bytes
Requests per second: 186.94 [#/sec] (mean)
Time per request: 26.746 [ms] (mean)
Time per request: 5.349 [ms] (mean, across all concurrent requests)
Transfer rate: 84.34 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 0 0.0 0 0
Processing: 15 27 17.0 24 235
Waiting: 15 27 17.0 24 235
Total: 15 27 17.0 24 235
Percentage of the requests served within a certain time (ms)
100% 235 (longest request)
As you see application can handle about 180 requests per second. Having in mind that this request during chat is send every 3.5 seconds. We can support upto 600 chatting users at the same time if my calculations are correct :) (180*3.5 = 630)
Small release compared to previous one, but it does one amazing thing. Now all messages from user or operators will be checked using same query. Last message ID algorithm for user was implemented. I think it's one of the last performance related part. Futher updates will include more features than refactoring. We now have really nice live support engine.
execute doc/update_db/update_17.sql and follow standard upgrade instructions.