This is also ver strange on the server with the entire table:
Load time so far: 0.95 seconds. Performing query: SELECT id,name,parent,validated,description,time,parentnames,parentids,numlinks,hide,lastlinktime,custom,lastedit,moderators,headerinfo,related,numsub,type,permissions,subscribers,subscriber,mixtypes,isalbum,orderlinks,totalcomments,ulsearchmax,ulsearchquery,ulsearchadult,alias,catcols,linkcols,dmozpath,sponsorlinks,views,customwrap FROM wsnl_categories WHERE parent=0 AND validated=1 AND hide=0 AND isalbum=0 ORDER BY name ASC LIMIT 0,100;
Number of rows is 56 for Resource id #24
Load time so far: 1.3 seconds. Performing query: SELECT id FROM wsnl_categories WHERE parent=0 AND validated=1 AND hide=0 ;
Number of rows is 56 for Resource id #25
Load time so far: 7.82 seconds. Performing query: UPDATE wsnl_sessions SET starttime='0' WHERE time < 15;
It seems it takes 7 seconds to get 56 categories :s
Hmmm i just emptied the entire category table and this is the resukt:
19 total queries This page was created in 1,1010019779205 seconds
1,1 second to load nothing
This is where it takes up allot of time for nothing?
Load time so far: 0.4 seconds. Performing query: SELECT id FROM wsnlinks_categories WHERE validated=1 AND hide=0 ORDER BY id DESC LIMIT 0,1;
Load time so far: 0.46 seconds. Performing query: SELECT name,value FROM wsnlinks_switches WHERE id>0 ;
And with some test data
Load time so far: 1,15 seconds. Performing query: SELECT id FROM wsnlinks_categories WHERE parent=0 AND validated=1 AND hide=0 ;
Number of rows is 344 for Resource id #43
Load time so far: 1,16 seconds. Performing query: SELECT id,name,parent,validated,description,time,parentnames,parentids,numlinks,hide,lastlinktime,custom,lastedit,moderators,headerinfo,related,numsub,type,permissions,subscribers,subscriber,mixtypes,isalbum,orderlinks,totalcomments,ulsearchmax,ulsearchquery,ulsearchadult,alias,catcols,linkcols,dmozpath,sponsorlinks,views,customwrap FROM wsnlinks_categories WHERE id=1 ;
Load time so far: 117,3 seconds. Performing query: SELECT id FROM wsnlinks_sessions WHERE memberid>0 ;
24 total queries This page was created in 122,9527721405 seconds
Suffice it to say that it obviously doesn't take 122 seconds to load in any reproducable situation no matter how much data, except possibly if you add a billion toplists or import data directly to the database without following the instructions to regenerate. Nobody else has had your problems.
0/5
1
2
3
4
5
This thread is closed, so you cannot post a reply.
Comments on Few Questions about WSN Links
Member
Usergroup: Customer
Joined: May 24, 2005
Total Topics: 1
Total Comments: 16
This is also ver strange on the server with the entire table:
It seems it takes 7 seconds to get 56 categories :s
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
Edit* Nevermind its the gzip compression which is buggy, when turned on you cant view any of the pages.
It's not a bug actually, read the manual entry.
Your admin queries total to 1-2 seconds. That's slower the usual, but not that bad.
How your categories query can be that slow, I wouldn't know. Maybe the table is indexed wrong or exceptionally badly optimized somehow.
Member
Usergroup: Customer
Joined: May 24, 2005
Total Topics: 1
Total Comments: 16
Offcourse this is just a small piece of it, but you will notice a lag allready, query time of 2 secondsup to 4 sec....
Attached Files:
Member
Usergroup: Customer
Joined: May 24, 2005
Total Topics: 1
Total Comments: 16
19 total queries
This page was created in 1,1010019779205 seconds
1,1 second to load nothing
This is where it takes up allot of time for nothing?
And with some test data
24 total queries
This page was created in 122,9527721405 seconds
Member
Usergroup: Customer
Joined: May 24, 2005
Total Topics: 1
Total Comments: 16
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
Suffice it to say that it obviously doesn't take 122 seconds to load in any reproducable situation no matter how much data, except possibly if you add a billion toplists or import data directly to the database without following the instructions to regenerate. Nobody else has had your problems.