Anthony, I hate to open this one back up again, but I just wanted to make you aware of what I am seeing. I have successfully upgraded to the 1.01 git version. When I run my application using inline push, it has to call a php file to pass the data. Every time that php file is called, it opens a new socket connection on my server. That file is also querying data from mysql and that is what is being passed. Just me sitting here frequently clicking submit and calling my php file via AJAX is causing my CPU to run around 87% utilization. If I have numerous people all doing the same thing, I can see where this would be slowing my server up. Tomorrow my application will get another big test and I will watch "netstat" and my CPU utilization during this time.
On Oct 15, 2:43 am, Anthony Catel <[email protected]> wrote: > Hey, > > There is not too many users. May be there is a bug somewhere. > > Does the aped proccess consume a lot of CPU during those freez ? > > Le 15/10/10 02:50, crusherdestroyer a crit : > > > Hi. I have been running into an interesting issue that has been > > causing me a little bit of trouble when using ape. We will have as > > many as 70 people on at once using same channel. We are using inline > > push to process data from MYSQL using PHP. On occasion, I will click > > on a button to trigger an event and it will freeze. I push it a > > couple more times to see if I can get it to continue and it will > > freeze for up to three seconds and then process all the backed up > > requests. I downloaded latest git version a few weeks ago and I'm not > > sure what version I'm on because I don't know how you find that out. > > I don't recall this happening before I switched from version 1, but > > that may have been because our customer base was around 35 at the > > time. > > > The same PHP file is triggered onclick for all users. Is this > > potentially the problem? I have used different browsers with the same > > result. When viewing firebug when this happens you can see where the > > process will literally "stick" before starting back up and process the > > backed up queue. > > > Do you think that there are too many simultaneous requests coming in > > and it's freezing it? Or is it possible it's something else? Any > > help on this would be appreciated. Thank you. > > > Ryan -- You received this message because you are subscribed to the Google Groups "APE Project" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/ape-project?hl=en --- APE Project (Ajax Push Engine) Official website : http://www.ape-project.org/ Git Hub : http://github.com/APE-Project/
