public inbox for [email protected]  

help / color / mirror / Atom feed

From: Dave Page <[email protected]>
To: Joshua D. Drake <[email protected]>
To: Guido Barosio <[email protected]>
Cc: Marc G. Fournier <[email protected]>
Cc: Josh Berkus <[email protected]>
Cc: John Hansen <[email protected]>
Cc: [email protected]
Cc: Jim C. Nasby <[email protected]>
Subject: Re: Infrastructure monitoring
Date: Sat, 14 Jan 2006 21:11:19 +0000
Message-ID: <BFEF1977.3B7B%[email protected]> (raw)
In-Reply-To: <[email protected]>




On 14/1/06 20:59, "Joshua D. Drake" <[email protected]> wrote:

> Hello,
> 
> I believe the biggest issue is not the monitoring but the fact
> that these machines are not managed.
> 
> All due respect to John (I believe he does the search) but if he
> is often on the road for 12 hours then someone else needs
> to be hosting those machines.
> 
> The machines need to be hosted by companies that manage
> servers. There are several in the PostgreSQL community and
> yes CMD is one of them.
> 
> I am not trying to take any kudos from anyone or suggest that
> they are not doing a bang up job. I am saying that all of the
> communities machines should be managed.
> 
> Outside of a hardware failure there is zero reason for these
> machines to have extended outages unless scheduled.

Well john has told me in the past he'd be happy to move the search to more
suitable servers. It's a big database handling a high volume of queries
though so a shared or old machine simply won't do.

I don't know how ASPseek will run on modern hardware, but the
far-less-efficient Mnogosearch became a gibbering wreck on a dual 3GHz Xeon
with 4GB RAM and what iirc was a 147GB RAID1 array.

Do you think Command Prompt might be able to help in this case? John can
give a better idea of the actual requirements of course - the only other
oddity that I can recall is that ASPSeek must be compiled with gcc 2.95 due
to some changes in the hashing functions in the STL in later versions which
cause index bloat.

Regards, Dave.

view thread (33+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Infrastructure monitoring
  In-Reply-To: <BFEF1977.3B7B%[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox