On Mar 25, 2014, at 8:46 AM, Matthew Spilich wrote:
> The symptom: The database machine (running postgres 9.1.9 on CentOS 6.4) is
> running a low utilization most of the time, but once every day or two, it
> will appear to slow down to the point where queries back up and clients are
> unable
On Sun, Feb 06, 2011 at 11:48:50AM +0100, felix wrote:
> BRUTAL
>
Did the changes work in your test environment?
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
On Mon, Oct 25, 2010 at 11:39:30AM -0700, Divakar Singh wrote:
> Thanks Ray,
> Already seen that, but it does not tell about storage requirement compared to
> Oracle. I find it takes 2 times space than oracle.
>
>
> Best Regards,
> Divakar
> ______
On Thu, Aug 06, 2009 at 09:12:22AM -0700, Joshua D. Drake wrote:
> Why aren't you using systemtap again?
1. significant solaris responsibilites
2. significant linux responsibilities
3. tool consolidation delusions
Can you drive dtace toolkit via systemtap?
--
Sent via pgsql-performance mailing
On Thu, Aug 06, 2009 at 11:01:52AM -0400, Tom Lane wrote:
>
> dtrace is available on Solaris and Mac OS X and probably a couple
> other platforms, but not Linux.
I wondered if anyone had given this a go:
http://amitksaha.blogspot.com/2009/03/dtrace-on-linux.html
--
Sent via pgsql-performanc
On Thu, Aug 06, 2009 at 12:50:51PM +1000, Ip Wing Kin John wrote:
> (running DTrace tool kit iofile.d script to show I/O wait time by
> filename and process)
Is the dtrace toolkit a viable product for a linux environment or
is it strickly Sun/Oracle?
--
Sent via pgsql-performance mailing list (p
I had such great hopes for this thread. "Alas, poor Yorick! I
knew him, Horatio ..."
On Thu, Jul 12, 2007 at 11:00:54AM -0400, Greg Smith wrote:
> On Thu, 12 Jul 2007, Gregory Stark wrote:
>
> >In any case I wouldn't think the use case for a feature like this would
> >actually apply in the
On Tue, Jun 19, 2007 at 10:49:01AM -0700, Y Sidhu wrote:
> On 6/19/07, Francisco Reyes <[EMAIL PROTECTED]> wrote:
> >
> >Campbell, Lance writes:
> >
> >> Francisco and Richard,
> >> Why ask about disk or raid? How would that impact any settings in
> >> postgresql.conf?
> >
> >If the user has 2 dis
On Mon, Jun 18, 2007 at 04:35:11PM -0700, Steve Atkins wrote:
>
> On Jun 18, 2007, at 4:09 PM, [EMAIL PROTECTED] wrote:
>
> The tricky bits are going to be defining the problem and creating the
> alogrithm to do the maths from input to output.
Why not methodically discuss the the alogrithms on
On Fri, Apr 27, 2007 at 02:40:07PM -0400, Kevin Hunter wrote:
> out that many run multiple postmasters or have other uses for the
> machines in question), but perhaps it could send a message (email?)
> along the lines of "Hey, I'm currently doing this many of X
> transactions, against this mu
On Wed, Feb 21, 2007 at 08:09:49AM -0800, Craig A. James wrote:
> I hope I didn't give the impression that these were the only thing to look
> at ... those four items just popped into my head, because they've come up
> repeatedly in this forum. There are surely more things that could be
> suspe
I'd like to have a toolbox prepared for when performance goes south.
I'm clueless. Would someone mind providing some detail about how to
measure these four items Craig listed:
1. The first thing is to find out which query is taking a lot of time.
2. A long-running transaction keeps vacuum from
On Thu, Jan 25, 2007 at 08:04:49AM -0800, Joshua D. Drake wrote:
>
> It really depends on the system. Most of our systems run anywhere from
> 10-25ms. I find that any more than that, Vacuum takes too long.
How do you measure the impact of setting it to 12 as opposed to 15?
-
On Thu, Jan 25, 2007 at 07:29:20PM +0900, Galy Lee wrote:
> so what is the principle to set them?
> - keep dead space lower than some disk limit
> - or keep the garbage rate lower than fillfactor
> or any other general principle?
How do you measure "dead space" and "garbage rate?"
I'm a newbe
14 matches
Mail list logo
