|
Tuesday, 01 May 2007 |
|
With flood prevention in place we almost have in place what required to make Avatar run 24/7 without interruption. We still need to tackle some issue on stability and complete our Cookie Jar :)
We are discussing about implementing some type of caching on Avatar but it won't be started before we are done with chunk transfer of HTML files implementation to make user feel faster response.
After taking a good look at our link substitution function, we did some changes and manage to make it about 10% faster.
We have a new build that capable of Chunked Transfer-Encoding. We still try to do more testing to make sure everything is OK before using it live on our server.
|
|
Last Updated ( Wednesday, 02 May 2007 )
|
|
|
Tuesday, 01 May 2007 |
|
If you visit Youtube or other video site, Avatar pretty much remove all the video files since they use javascript to display video file instead of using embed tag. We are working on the solution for that too and will integrate it to Avatar soon. |
|
Last Updated ( Tuesday, 01 May 2007 )
|
|
|
Tuesday, 01 May 2007 |
|
We need to change Avatar work flow a bit. Right now we can't boot a request if it take too long to complete. We just fork Avatar so it now only fire up necessary thread and it's a good time to implement our flood prevention system. So please be patient while we implement this :)
We have automatic ban in place that will banned an IP for a while if it hammer Avatar too hard :) |
|
Last Updated ( Tuesday, 01 May 2007 )
|
|
|
Monday, 30 April 2007 |
|
Avatar have been running fine Saturday and Sunday but enter Monday and it's a whole new game. We have request spike that slowly bringing down Avatar. We are working on some kind of flood prevention that we hope can handle weekday traffic more smoothly.
We are seeing some great facts on Monday. Some IP just going crazy by doing almost 200 connections to Avatar making Avatar bogged down with processing request. Along with flood protection we also gonna take a good look at our Link Substitute procedure. It seems we still can optimize it.
|
|
Last Updated ( Monday, 30 April 2007 )
|
|
|
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 )
|
|
|
|
<< Start < Prev 1 2 3 4 5 6 Next > End >>
|
| Results 41 - 50 of 54 |
News 
