[Project_owners] Yesterdays Debacle

Biju G C bijumaillist at yahoo.com
Thu Oct 23 16:43:46 EDT 2003


after I used 

 header("Expires: " . date("r",time() + 60*60*24));

(It cashes for 24 hours)
and i was getting a better performace in QuickManager.

Still if you want to stop people from using QuickManager for a while
I can ask them do that.

> One has been the issue of http://texturizer.net/firebird/extensions/ 
> stealing bandwidth and CPU from Mozdev. This as I understand has been 

texturizer.net is our friend David Tenser's site
he is very much dedicated in promoting mozilla products.
hence a great contributor to our goal.
Because of http://texturizer.net/firebird/extensions/
many people is knowing about us

I think HE WAS ASKED to use "DATABASE"
and many of us know he is using extensions.js.php 

so i feel it is not "stealing".
Why we want hurt feeling of such a GREAT GUY.

Regarding band width, This not an isolated problem at 
extensions.js.php it is a mozdev.org wide issue.

=== following is relevent part from my post at [database]

None of the web pages at mozdev has a expiry time, and last modified time 
is set to the visit time (ie, the generated time).  
This makes every page to refresh on each visit. 
We dont notice this because most pages are small.

But this become noticeable in big pages like 
as well as on pages with long notes like 

I am not passing blame on anybody, 
if somebody should be blamed I will be in that list 
because even after knowing I never pushed this issue hard 
or brought it to notice of mozdev admins. 

But on other hand by making extensions.js.php and birdthemes.js.php 
CLAV is doing GREAT HELP. 
I really appreciate it !!!!

But whether it is JS or HTML, serving big pages with 
This is what I learned from my experience.

we should serve it as static file.

Always remember WWW was created to serve file documents, 
but not an output of application.
(even thought majority of sites are doing that now)


 --- Pete Collins <pete at mozdev.org> wrote: 
> As many of you may have noticed, Mozdev has been performing slow as 
> shit. Yesterday, I shut down cvs right before I burnt out myself.  The 
> load on the box is minimal, yet we appear not to be able to get web 
> pages out the door. I have not asertained the entire source of the 
> bottleneck.
> One has been the issue of http://texturizer.net/firebird/extensions/ 
> stealing bandwidth and CPU from Mozdev. This as I understand has been 
> resolved. If there are any projects that are generating data from db 
> reads on Mozdev, we need to know about it.
> I know about extensionroom, theme, database and quickmanager projects.
> *PLEASE* remove all php generated db reads. Any xml data *must* be 
> cached. Daily preferrred.
> After this has been sorted out, then we can reevaluate to asertain if 
> this was indeed the source of the bottleneck. If this helps, then we 
> know it was part of the problem and we need to continue looking for the 
> root.
> Also, understand, I am a volunteer. When shit like this happens, it 
> sucks away very valuable time I just don't have chasing these issues 
> that could have been avoided by better communication.  Someone mentioned 
> that cdn knows about these projects. Yes cnd is an admin, but he is not 
> the greatest communicator and usually relies on me reading his mind. :)
> So "pretty please with sugar on top". Run this stuff by admin at mozdev.org 
> first before implementing. We are here to enable you guys, but if the 
> results of your actions render Mozdev unusable, then it ends up hurting 
> the comunity.
> This has been a Mozdev disservice announcement.
> --pete
> -- 
> Pete Collins
> www.mozdev.org
> www.mozdevgroup.com
> _______________________________________________
> Project_owners mailing list
> Project_owners at mozdev.org
> http://mozdev.org/mailman/listinfo/project_owners 

Want to chat instantly with your online friends?  Get the FREE Yahoo!
Messenger http://mail.messenger.yahoo.co.uk

More information about the Project_owners mailing list