So, I am very excited about this component. It is VERY useful and I am glad we purchased it.

However, it has come to our attention that it is a bandwidth HOG. the sync.php file was accessed almost twice EVERY SECOND in a 36 hour period.

I need this fixed asap. What can we do?



This image is hidden for guests. Please login or register to see it.

This really needs to be addressed. Is there no one around that has an answer for this?

Hi Chas,

In regards to your question; JLive! Chat is not hogging your bandwidth, it is simply synchronizing with your webserver. It synchronizes with your webserver every few seconds, which is why we highly recommend "Disabling Webserver logging" for JLive! Chat requests:

www.cmsfruit.com/joomla-live-chat-docume...html#disable_logging


Alternatively, you can run JLive! Chat in hosted mode at the UltimateLiveChat.com if you do not want to run JLive! Chat on your webserver, or if you can't make any webserver changes.

We are currently working on the next major release of JLive! Chat, which introduces many new powerful features and will also have much better performance. We expect to have the new version released within the next month or so.


Best Regards,
John

Please ensure you also have Keep-Alive enabled on your webserver and that your keep-alive timeout is set to at least 3 seconds so that subsequent requests to your webserver uses the same connection.

I implemented your fix, and it seems to be working, but this is the response I'm getting from my web host.
******************************************************
Chas,

Disabling logging doesn't fix the source of the issue, the problem is how the component interacts with itself over HTTP. That's nothing we have any control of, but rather a design issue with the script itself.

I didn't write nor have I reviewed the code for the component so I can't say if they have better alternatives. However, I can say that I've never had to disable logging to hide bandwidth for automated processes since they're usually run via cron using CLI which eliminates the HTTP overhead.

The "fix" we implemented can be deployed on any of your domains as needed but isn't a server-wide default. Would you like us to implement this on angeladoptioninc.com?

----
Ben Johnson
Rochen Limited
******************************************************

What do you think? Is there a way to modify the script so that the sync.php file is called using cron and CLI PHP?

Hi Chas,

I believe there may be some confusion on this topic... you are not disabling logging on your webserver overall... you ONLY need to disable logging for requests that JLive! Chat makes to your webserver... some hosting providers have an issue with people running chat software on there server because chat softwares tend to make many requests and tend to use webserver resources (like CPU)... now the issue your hosting provider is reporting you, is most probably the fact that JLive! Chat is consuming some CPU resources... it doesn't actually consume "bandwidth" per say, because it is really not transferring large amounts of data... the way JLive! Chat works is pretty straight forward... it makes one connection to your webserver using keep-alive, and it syncs with your website every few seconds... there are currently some performance bottlenecks at the CPU level with JLive! Chat... we are currently working on the next major release of JLive! Chat which corrects all performance bottlenecks... we expect to have it released in the next month or so... however, please be advised that the synchronization process for JLive! Chat will still be the same as it is now... so you will still need to exclude JLive! Chat from your webserver logging... the CPU performance bottlenecks will be resolved in the new version which may solve the issue your hosting provider is having with JLive! Chat or it may not... they may still have an issue with you running chat server software on your website, if you are consuming more server resources then they want you to... I can't tell you that for sure, thats out of our control... If that is the case, and your hosting provider is simply saying that running this software on your website is not allowed because it is consuming too much resources, or if you can't exclude JLive! Chat requests from your web server log, then the only solution left would be to use the hosted version of JLive! Chat at:

http://www.ultimatelivechat.com


By using the hosted version of JLive! Chat, there are some drawbacks, like not being able extensively customize JLive! Chat because you won't be able to access the backend PHP files... but unless those are your intentions, the hosted version is perfect for someone in your scenario... that way you don't have to deal with all the technicalities of JLive! Chat, we take care of all that for you.

Hope that helps!
John