(01-18-2013 03:50 AM)Serena Stroikavskoi Wrote: I still differ because php, mysql, l2l is all different scripting languages, they still have to interpret and communicate to each other. That's why it's a server side script. It functions directly on the server much like a program. We all know how we complain about those too. When the translator is broke or sick, it slows response time. When you take that into play and the bandwidth between say your cable company and mine along with DNS you have slower response time. Yes the they are on linden lab servers hosted by someone else but the communication between scripting still has to talk to each other in-world as well as the cattery.
When the translator is sick we all see the effect.
Serena,
LSL only works in-world. php and MySQL work OUTSIDE of SL. Tad is correct. This website has absolutely *nothing* to do with LSL and the statistics that Tad was showing are for the slow response of the website are not affected by anything our cats do or don't do in-world.
When your cats are in cattery, they don't even *exist* in-world, so they don't rely on LSL. All calculations, etc. are done by the software backing the cattery, which one assumes is php and any code-behind method used. ( I tend to work in MS environs, so I'm not 100 percent sure that php uses any hidden code-behind as is possible with aspx, etc., but if it does, that is where the work will be done. ).
Tad,
I have noticed that once the pedigree is retrieved, that you can apply/change filters *very* quickly, which makes me presume the SQL for the page retrieves the whole dataset and then filters are applied 'on the fly' as the actual page display is built. This makes for slow initial load but quick updates, but it *also* uses a lot of extra storage to hold the whole dataset. This may be part of the performance issues you're seeing.
