Shouldn't have to do that if the thread is indexed wisely. Even just having post-numbers as an index of some sort for a thread allows selecting specific posts only to be returned for display.
I took that to be the case.It is indexed on postid (and several other things). I said "or at least look at an index containing all the posts". Which you do.
I took that to be the case.
How about one of these wot I get to play with daily: http://h20195.www2.hp.com/V2/GetPDF.aspx/5982-9830EN.pdf
64 processor Integrity system with 2TB of shared memory.
I'm certainly not an expert on any of this, but couldn't we just eliminate the search function and just keep the google search?
No because the search function does a bunch of things google doesn't.
I took that to be the case.
How about one of these wot I get to play with daily: http://h20195.www2.hp.com/V2/GetPDF.aspx/5982-9830EN.pdf
64 processor Integrity system with 2TB of shared memory.
64-bit is nice but not critical; the Linux filesystem cache can grow to 64GB (I think) even on a 32-bit system, and while it's not quite as efficient as MySQL's own buffers (assuming you're using InnoDB), it gets the job done.
There are indeed funny RAM addressing tricks. It's called PAE (physical address extension). Although any one program can still only see 4GB of memory, the operating system can support up to 64GB in total.Wait... I'm afraid I'm missing something here, and if I am, I'm open to correction. But: How can the Linux filesystem cache grow to 64 gigs on a 32 bit system? If we're talking about cache residing in RAM, then the 4 GB limitation still applies because we're (presumably) talking about x86 hardware, and that limit is a physical one imposed by the addressing scheme, not an software one imposed by the operating system. So unless there's some funny RAM addressing tricks I'm unaware of, it still applies. Are there some tricks to get around the limitation? Or are we not talking about caching to RAM here?
Maybe, but I think a nice cost-benefit analysis would be good here. The search function may be able to do a few nifty things, but it's very slow and notoriously unreliable. I would be willing to give up any benefits the search function has if it would stop these server issues for good, since there is already a search function supplied by google.
Oh, really?The Google search cannot see the members only areas.
JREF Forum
11 Feb 2009 ... Aquarium of Blood Game Thread. by Damien Evans. Today 06:17 AM Go to
last post. 23528, 738675. Humor · Continuation-squared: The Three Word ...
forums.randi.org/forumindex.php - 58k - Cached - Similar pages -
Members Only - JREF ForumIn order to show you the most relevant results, we have omitted some entries very similar to the 2 already displayed.
Aquarium of Blood Game Thread. by Giggywig. Today 06:39 PM Go to last post. 23428,
724562. Humor · I think I have you now... by The Drain ...
forums.randi.org/forumdisplay.php?s=&daysprune=&f=20 - 30k - Cached - Similar pages -
More results from forums.randi.org »
Oh, really?
Then how do you explain the following?
Google: Results 1 - 2 of 2 for "Aquarium of Blood Game". (0.44 seconds)
I've used Search on a number of occasions. Sometimes it finds what I want, sometimes it doesn't.I don't believe I ever found anything I set out to find using the Search utility.
Anyone else similarly underwhelmed?
Or edit the robots.txt file (or whatever) and let Google index the members area
I don't believe I ever found anything I set out to find using the Search utility.
Anyone else similarly underwhelmed?
I think, in the absence of substance in your statements, that there's a distinct possibility that you're wrongI think the reason Google can't index the members only sections is because Google spiders can't log in.Or edit the robots.txt file (or whatever) and let Google index the members area
User-Agent: *
Disallow: /latexrender/
Disallow: /forumlive/ajax.php
Disallow: /forumlive/attachment.php
Disallow: /forumlive/calendar.php
Disallow: /forumlive/cron.php
Disallow: /forumlive/editpost.php
Disallow: /forumlive/global.php
Disallow: /forumlive/image.php
Disallow: /forumlive/inlinemod.php
Disallow: /forumlive/joinrequests.php
Disallow: /forumlive/login.php
Disallow: /forumlive/member.php
Disallow: /forumlive/memberlist.php
Disallow: /forumlive/misc.php
Disallow: /forumlive/moderator.php
Disallow: /forumlive/newattachment.php
Disallow: /forumlive/newreply.php
Disallow: /forumlive/newthread.php
Disallow: /forumlive/online.php
Disallow: /forumlive/poll.php
Disallow: /forumlive/postings.php
Disallow: /forumlive/printthread.php
Disallow: /forumlive/private.php
Disallow: /forumlive/profile.php
Disallow: /forumlive/register.php
Disallow: /forumlive/report.php
Disallow: /forumlive/reputation.php
Disallow: /forumlive/search.php
Disallow: /forumlive/sendmessage.php
Disallow: /forumlive/showgroups.php
Disallow: /forumlive/subscription.php
Disallow: /forumlive/threadrate.php
Disallow: /forumlive/usercp.php
Disallow: /forumlive/usernote.php
Disallow:/forumlive/vbimagehost.php
User-Agent: Slurp
Disallow: /forumlive/
User-Agent: Referer Karma/2.0
Disallow: /forumlive/
Maybe you ought to read up on White Hat and Black Hat SEO and then think againIn order to make everything visible to Google, it would all have to be visible to everyone.
robots.txt has nothing to do with it.I think, in the absence of substance in your statements, that there's a distinct possibility that you're wrong
http://www.randi.org/robots.txt
I think, in the absence of substance in your statements, that there's a distinct possibility that you're wrong
http://www.randi.org/robots.txt
Maybe you ought to read up on White Hat and Black Hat SEO and then think again
Let me say, on behalf of several in the Forum:
What?!
But that's okay, we assume the tech-savvy are arguing about something meaningful.
Just tell us how much money to send where...
Thanks, MK
Thanks for all the input. We're looking at quotes now, and hopefully we'll be setting up a new server this week.
There will be an update on the problems very soon (days).