Hey!
Just wanna say, if Firebug did not exist, the world of web development
would be depressing.
I'm a student at the University of Waterloo and was writing some
server load tests. This is a relatively specialized case however, it's
a bug no less.
I've found that with certain conditions with AJAX calls, the times are
way off of what's going on. At first I thought it was a performance
issue with the Javascript as it's not a very quick language, however I
monitored my network traffic with Wireshark and sure enough, my
results in Javascript were correct, therefore the times given in
Firebug are way off.
"test" is the id of a <tbody> within a <table>.
My function:
function test1(numbytes) {
xmlHTTP = new XMLHttpRequest();
xmlHTTP.onreadystatechange=function() {
if (this.readyState==4) {
delta = (new Date).getTime()-start;
this.responseText=="1" ? success = "Success" : success =
"Fail";
document.getElementById("test").innerHTML+="\
<tr>\
<td>1</td>\
<td>"+numbytes+"</td>\
<td>"+delta+"</td>\
<td>"+success+"</td>\
</tr>";
if (numbytes<Math.round(134217728*(4/5))) {
test1(parseInt(numbytes)+10000);
}
}
};
start=(new Date).getTime();
xmlHTTP.open("GET","/wktrmtest/svyside.py/test1?
x="+numbytes,true);
xmlHTTP.send(null);
}
This is a memory stress test where numbytes are the number of bytes to
be stored (arbitrary). I found that the range where Firebug gets a bit
buggy is around 1s response time between server and client. I'm not
sure why that is as I've found Firebug to be pretty reliable
otherwise. The server side programs are done in Python (hence
the .py).
Cheers!
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Firebug" 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/firebug?hl=en
-~----------~----~----~----~------~----~------~--~---
