In New Relic, go back a half hour before the problem started so you can't
see that this spike happened and send the same screenshot in. My guess is
you have increased activity hitting the DB. Do you have pgbouncer or some
kind of connection pooling sitting in front? 198 open server connections
coul
On Mon, Mar 31, 2014 at 3:25 AM, Niels Kristian Schjødt
wrote:
> I'm running postgresql 9.3 on a production server. An hour ago, out of the
> "blue", I ran into an issue I have never encountered before: my server
> started to use CPU as crazy. The server is a standard ubuntu 12.04 LTE
> install
Thanks, I don’t think overheating is an issue, it’s a large dell server, and I
have checked the historic CPU temperature in the servers control panel, and no
overheating has shown.
Zone_reclaim_mode is already set to 0
Den 31/03/2014 kl. 16.50 skrev Scott Marlowe :
> On Mon, Mar 31, 2014 at 8
Yes, I could install “perf”, though I’m not familiar with it. What would i do? :-)
Niels Kristian SchjødtCo-founder & DeveloperE-Mail: nielskrist...@autouncle.comMobile: 0045 28 73 04 93www.autouncle.comFollow us: Facebook | Google+ | LinkedIn | Twitter Get app for: iPhone & iPad | Android
Tom and Shawn,
Thanks for the feedback. This has been helpful. It's worth noting that
I was spiking this out on my local box using default memory utilization
settings. I'll revisit this once we get our production box set up. It's
good to know what the best practices are around the enable
On Mon, Mar 31, 2014 at 8:24 AM, Niels Kristian Schjødt
wrote:
>
> Thanks, this seems to persist after a reboot of the server though, and I have
> never in my server's 3 months life time experienced anything like it.
Could it be overheating and therefore throttling the cores?
Also another thing
On Mon, Mar 31, 2014 at 9:24 AM, Niels Kristian Schjødt <
nielskrist...@autouncle.com> wrote:
> Thanks, this seems to persist after a reboot of the server though, and I
> have never in my server's 3 months life time experienced anything like it.
>
huh. Any chance of getting 'perf' installed and
Thanks, this seems to persist after a reboot of the server though, and I have never in my server’s 3 months life time experienced anything like it.
Niels Kristian SchjødtCo-founder & DeveloperE-Mail: nielskrist...@autouncle.comMobile: 0045 28 73 04 93www.autouncle.comFollow us: Facebook | Google+
Christopher Jackson writes:
> tl;dr - How can I speed up my count-distinct query?
EXPLAIN doesn't provide a lot of visibility into what the Aggregate plan
node is doing, but in this case what it's doing is an internal sort/uniq
operation to implement the DISTINCT. You didn't say what value of
On Mon, Mar 31, 2014 at 5:25 AM, Niels Kristian Schjødt
wrote:
> I'm running postgresql 9.3 on a production server. An hour ago, out of the
> "blue", I ran into an issue I have never encountered before: my server
> started to use CPU as crazy. The server is a standard ubuntu 12.04 LTE
> install
> tl;dr - How can I speed up my count-distinct query?
You can't.
Doing a count(distinct x) is much different than a count(1), which can simply
scan available indexes. To build a distinct, it has to construct an in-memory
hash of every valid email, and count the distinct values therein. This
I'm running postgresql 9.3 on a production server. An hour ago, out of the
"blue", I ran into an issue I have never encountered before: my server started
to use CPU as crazy. The server is a standard ubuntu 12.04 LTE installation
running only Postgres and Redis.
The incident can be seen on the
12 matches
Mail list logo
