Hello Ryan, Looking at our error logs for the last 2 days, I would have to save the situation is improved with the advent of 1.3.1, but certainly not fixed. From the standpoint of our app., being forced to supply all our mp3, png, etc. files out of the database enormously increases our exposure to the timeout 'feature'. If we could have real files (which one would hope didn't suffer from some similar timeout problem) I don't think we would have any substantial problem. As it stands, I still see 30 or so timeout entries in the log per day. That number is still a bit too high for me.
On Feb 12, 5:28 am, ryan <[email protected]> wrote: > hi phtq! out of curiosity, would you consider 1.3.1's extended retries > a "fix" for the timeout "bug"? > > http://googleappengine.blogspot.com/2010/02/app-engine-sdk-131-includ... > > (of course, as djidjadji mentioned, it's not really a bug as much as > an unfortunate fact of life in distributed systems, and 1.3.1's > extended retries aren't a fix as much as a mitigating factor. still, > i'm curious about the perception.) > > On Jan 26, 2:30 pm, phtq <[email protected]> wrote: > > > > > Our application error log for the 26th showed around 160 failed http > > requests due to timeouts. That's 160 users being forced to hit the > > refresh button on their browser to get a normal response. A more > > typical day has 20 to 60 timeouts. We have been waiting over a year > > for this bug to get fixed with no progress at all. Its beginning to > > look like it's unfixable so perhaps Google could provide some > > workaround. In our case, the issue arises because of the 1,000 file > > limit. We are forced to hold all our .js, .css, .png. mp3, etc. files > > in the database and serve them from there. The application is quite > > large and there are well over 10,000 files. The Python code serving up > > the files does just one DB fetch and has about 9 lines of code so > > there is no way it can be magically restructured to make the Timeout > > go away. However, putting all the files on the app engine as real > > files would avoid the DB access and make the problem go away. Could > > Google work towards removing that file limit? -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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/google-appengine?hl=en.
