First off, thanks big time for pointing me towards repoze.profile. I have integrated it into my app and love it.
The total time for a request without DB stuff is about .855 CPU seconds The total time for a request with DB suff is about 1.470 CPU seconds These numbers are saying that the entire pylons request/response cycle is only taking 1.47sec, but my client sits there waiting for a request for about a minute, even when the client is being run on the same machine. Could the response be getting tied up in the network layer? Why would my use of SQLAlchemy and Mysql interfere with how long it takes a response to get sent to a client? I have never looked at network traffic directly before, but it seems like that is what I need to do next. I want to find out exactly when the request is being sent over the wire. A ny suggestions on how to proceed? On Mar 3, 3:26 pm, Paweł Stradomski <[email protected]> wrote: > W liście Bryan z dnia wtorek 03 marca 2009: > > > Inside of an XMLRPCController I have a function that inserts items > > into a database, and returns 'OK' to the client if everything works. > > Everything runs quickly and correctly, the rows are inserted into the > > DB, but pylons hangs for about a minute when generating the response. > > The client hangs there waiting for a response while pylons does > > *something*. > > Maybe try to profile your application to check where it spends that time? Try > repoze.profile. > > -- > Paweł Stradomski --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
