LQ Suggestions & Feedback Do you have a suggestion for this site or an idea that will make the site better? This forum is for you.
PLEASE READ THIS FORUM - Information and status updates will also be posted here. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
03-06-2006, 10:18 AM
|
#1
|
Senior Member
Registered: Dec 2003
Distribution: Debian
Posts: 3,178
Rep:
|
"My posts" and "My threads" should be exempt from the wait time before searches
Quote:
This forum requires that you wait 40 seconds between searches. Please try again in 40 seconds.
|
I often find myself waiting 40 seconds just to click "My Posts". I frequenty use this feature to locate threads I've posted in because I don't like the subscription feature.
Please exempt the "My Posts" and "My Threads" from the search wait time between posts.
|
|
|
03-06-2006, 11:35 AM
|
#2
|
Senior Member
Registered: May 2004
Location: Albuquerque, NM USA
Distribution: Debian-Lenny/Sid 32/64 Desktop: Generic AMD64-EVGA 680i Laptop: Generic Intel SIS-AC97
Posts: 4,250
Rep:
|
There is probably a trade-off for efficiency on a heavily used server like this one. Searches absorb lots of bandwidth. If removing the time limit between searches would have a negative effect on overall performance, that would NOT be a good thing. I occasionally have the same experience, but 40 seconds is probably not a terrible thing.
|
|
|
03-06-2006, 06:03 PM
|
#3
|
Senior Member
Registered: May 2002
Location: Horsham Australia
Distribution: elementary os 5.1
Posts: 2,479
Rep:
|
Like your sig, rickh.
I wonder how easy this would be to implement, Hari? Sounds easy enough though, and yeah, the 40 second delay ON JUST your posts could be reasonably removed- hari's not asking for the delay to be removed, rickh. I wonder if a check box could be set up so that you could tick to search just your posts.
titanium_geek
|
|
|
03-06-2006, 06:14 PM
|
#4
|
Senior Member
Registered: May 2004
Location: Australia
Distribution: Gentoo
Posts: 3,545
Rep:
|
Quote:
the 40 second delay ON JUST your posts could be reasonably removed
|
Why? It still puts the same demand on the server and judging by the average speed of search these days, I'm guessing that it's probably in the "too much" category. I feel your pain but I'm going to side with the Negative team here, the server seems to be under enough load as it is and allowing this would allow the couple of hundred very active members on the forum to kick the db in the head during high traffic periods.
An alternative is to start a donation drive and try and get Jeremy enough money for a new server with a crapload of RAM so he can have a dedicated db server. Load the db into RAM and set up his indexes properly and you could turn the wait off for all users all the time
|
|
|
03-06-2006, 06:32 PM
|
#5
|
Senior Member
Registered: May 2004
Location: Albuquerque, NM USA
Distribution: Debian-Lenny/Sid 32/64 Desktop: Generic AMD64-EVGA 680i Laptop: Generic Intel SIS-AC97
Posts: 4,250
Rep:
|
Quote:
...Load the db into RAM and set up his indexes properly and you could turn the wait off for all users all the time
|
... or put in a search engine with boolean logic
|
|
|
03-06-2006, 07:03 PM
|
#6
|
Senior Member
Registered: May 2004
Location: Australia
Distribution: Gentoo
Posts: 3,545
Rep:
|
Quote:
Originally Posted by rickh
... or put in a search engine with boolean logic
|
But thats a vB thing. I recall see a post a while ago about what Jeremy had done to optimise searching as best he could although it could have been for before the vB3 update...
If so, then perhaps thats something that could be added to this thread I still like my idea though heh, I've always wanted that much memory to play with
|
|
|
03-06-2006, 09:10 PM
|
#7
|
Senior Member
Registered: Dec 2003
Distribution: Debian
Posts: 3,178
Original Poster
Rep:
|
Quote:
Why? It still puts the same demand on the server and judging by the average speed of search these days,
|
You're wrong, technically. There's a definite qualitative difference between a full text search and a MySQL query which goes "SELECT * FROM table WHERE user_id=value";
Only a Full text search on a MySQL database would be hefty one the server and one can justify the wait time. Maybe just limit the wait time to full text searches.
Last edited by vharishankar; 03-06-2006 at 09:11 PM.
|
|
1 members found this post helpful.
|
All times are GMT -5. The time now is 05:00 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|