Is 20,000 links using the standard version of Links 2.0 (not SQL) to many links for it to handle...

I recently tried building the pages, and used 30% of the servers processor time. This inturn got me a severe warning about using links2 on their server...

what should I do.
Is this going to happen every time I build, and open every server???

Some suggestions:

1) Use the modified codes located in the Thread in the LINKS Modification Forum that breaks up the Building and Verifying files into smaller steps.

2) Take out some of your interactive options, like rating.

3) Switch Web Hosting companies.

Regards,

------------------
Eliot Lee
Founder and Editor
Anthro TECH, L.L.C
http://www.anthrotech.com/
info@anthrotech.com
==========================
Coconino Community College
http://www.coco.cc.az.us/
Web Technology
Coordinator
elee@coco.cc.az.us

i think eliot.. you forgot number 4...

4) BUY LINKS SQL...

not many actually go on that route do they?

OH.. have i ever told you review.cgi will totally not work on flatfile after about 30,000 reviews and ratings.. (50/50)

that's sort of why i'm making it in MySQL not flatfile anymore..

amazingly.. geturl.cgi still works even if it's at.. hmm... [checking] 31232 links.. i don't think spider.cgi works anymore.. too many.. and it's mainly cause of the bug i never fixed.. it just kept growing cause i didn't fix it.. oh well

jerry

[This message has been edited by widgetz (edited September 28, 1999).]

OK - With this SQL thingamajig, is there much difference with MSQL and MYSQL in limitations...

If I make mods etc in MySQL, will many people be unable to use it cause they only have MSQL????

Anyway... I am just gonna make em... if I need a feature from MySQL I'll use it

------------------
Michael Bray
....
Review your webhost, or find a new one at http://www.webhostarea.com

mSQL has a much more limited set of commands than MySQL... meaning (pretty much) if something works on mSQL it will work on MySQL (people have reported changes as simple as s/mSQL/mysql/g to make it work.

The reverse is _not_ true. LinkSQL won't work on mSQL because it's missing some of the commands necessary.

There is a good book out on mSQL/MySQL (about 2 months old) that goes over the differences in detail.