|
Friday, 27 April 2007 |
|
After scratching our head for days because of random lock up that happen randomly which we can't even pinpoint the cause, we decide to change the component that handle incoming connection and voila... it runs more smoothly and use a lot less cpu power. Let's see if it can survive the real hardcore testing on Saturday.
Although there is not a lot of code got changed, we still need to to figure out what's broken when we changed our component. We just fixed login issue and some other minor stuff. |
|
Last Updated ( Friday, 27 April 2007 )
|
|
|
Tuesday, 24 April 2007 |
|
Avatar have been running almost 6 hours with no crash and deadlocks serving almost 150,000 requests and counting. With stability issue almost behind us now, though we still need a way to recover from crash, we are looking to improve Avatar cookie management. It seems we need some kind of cookie jar that enable us to restart Avatar without losing it's current cookies collection.
We need to cut down our thread usage from 3 threads/request to just 1. It will save tons of memory consumption. Right now we are using almost 1GB for 600 threads. We were able to cut it down to 600MB by reducing it to 2 threads/request with little coding. Reducing it to 1 thread/request are gonna need more coding and testing. |
|
Last Updated ( Wednesday, 25 April 2007 )
|
|
|
Monday, 23 April 2007 |
|
Right now our implementation on HTML files is read all data from target website, do link substitution, gzip encode it, then send it to user. The problem of this method is the response seems slower to user for HTML files. Other files doesn't suffer this problem since we pretty much stream it to user as soon as we got it from target website. Right now we are trying to code method to partially process HTML and transfer it as soon as possible to user but it will mean no more gzip encoding since we will send the data in chunks.
In the end it will took approximately the same process time and larger file size but response will feel faster to users.
We are coding priority system to ensure HTML and CSS files got higher priority than other files to ensure faster response when there are more requests than threads available. |
|
Last Updated ( Tuesday, 24 April 2007 )
|
|
|
Monday, 23 April 2007 |
|
We finally found the last piece of Avatar puzzle which will enable us to finally have a stable working version of Avatar. Thank you for your patience :)
We have done careful inspection on our codes to make sure all our new implementation is in place so Avatar run as intended. Our last build got a great potential since it didn't show any sign of deadlocks, yet.
|
|
Last Updated ( Monday, 23 April 2007 )
|
|
|
Friday, 20 April 2007 |
|
We have implemented some of things we think will improve stability of Avatar. Right now it's running the latest version and hopefully it will withstand the next hardcore stress test session. We are sorry for lots of down time on ipbender.com service and working hard to improve it :) |
|
|
Wednesday, 18 April 2007 |
|
Deadlock is one of the most common problem in multithread application. Even a slightest error can cause entire application going down or going nowhere. We have fixed deadlocks on Avatar and it have been running and serving almost 100,000 request now without breaking down.
After putting Avatar on real hardcore stress testing, we collect a great amount of understanding of flaws that need to be fix.
|
|
Last Updated ( Thursday, 19 April 2007 )
|
|
|
|
<< Start < Prev 1 2 3 4 5 Next > End >>
|
| Results 45 - 54 of 54 |
