On 07/14/2012 09:21 AM, B Sreejith wrote:
Dear Sergev,
We have around 15 to 18 separate products.What we are told to do is to
check the scalability of the underlying DB of each product (application).
That's the requirement.Nothing more was explained to us.That's why I
said earlier that I am c
On 07/13/2012 03:50 PM, Stanislaw Pankevich wrote:
MySQL: the fastest strategy for cleaning databases is truncation with
following modifications:
1) We check is table is not empty and then truncate.
2) If table is empty, we check if AUTO_INCREMENT was changed. If it
was, we do a truncate.
For My
On 07/11/2012 07:46 PM, Andy Halsall wrote:
I've written an Immutable stored procedure that takes no parameters
and returns a fixed value to try and determine the round trip overhead
of a query to PostgreSQL. Call to sp is made using libpq. We're all
local and using UNIX domain sockets.
PL/
Dear Robert,
We need to scale up both size and load.
Could you please provide steps I need to follow.
Warm regards,
Sreejith.
On Jul 14, 2012 1:37 AM, "Robert Klemme" wrote:
> On Tue, Jul 10, 2012 at 10:21 AM, Sreejith Balakrishnan
> wrote:
> > Is there any tool or some sort of script availabl
Dear Sergev,
We have around 15 to 18 separate products.What we are told to do is to
check the scalability of the underlying DB of each product (application).
That's the requirement.Nothing more was explained to us.That's why I said
earlier that I am confused on how to approach this.
Regards,
Sree
On Tue, Jul 10, 2012 at 10:21 AM, Sreejith Balakrishnan
wrote:
> Is there any tool or some sort of script available, for PostgreSQL, which
> can be used to measure scalability of an application's database. Or is there
> any guideline on how to do this.
>
> I am a bit confused about the concept of
On Fri, Jul 13, 2012 at 3:22 PM, Eoghan Murray wrote:
> This is with `enable_material=off`, with `enable_material=on` it also
> doesn't go for the Merge Join, but the Materialize step pushes it up to over
> 7,000ms.
I think this one could stem from what Tom observed, that the rowcount
estimate is
On Tue, Jul 10, 2012 at 12:21 PM, Sreejith Balakrishnan
wrote:
> Dear @,
>
> Is there any tool or some sort of script available, for PostgreSQL, which
> can be used to measure scalability of an application's database. Or is there
> any guideline on how to do this.
"scalability of an application's
Eoghan Murray writes:
> I'm upgrading from 8.4 to 9.1 and experiencing a performance degradation on
> a key query with 2 views and 2 tables.
I think the core of the problem is the lousy rowcount estimate for the
result of the edited_stop_2 view: when you've got 1 row estimated and
almost 1 ro
On Fri, Jul 13, 2012 at 1:28 PM, Eoghan Murray wrote:
> Thank you Claudio,
>
> I haven't touched the 9.1 configuration (with the exception of toggling the
> enable_material setting). http://pastebin.com/nDjcYrUd
> As far as I can remember I haven't changed the 8.4 configuration:
> http://pastebin.
Dear Friends,
Is there a tool available to perform Data Model review, from a performance
perspective?
One which can be used to check if the data model is optimal or not.
Thanks,
Sreejith.
Andy Halsall writes:
> I've written an Immutable stored procedure that takes no parameters and
> returns a fixed value to try and determine the round trip overhead of a query
> to PostgreSQL. Call to sp is made using libpq. We're all local and using UNIX
> domain sockets.
> Client measures ar
On Fri, Jul 13, 2012 at 11:11 AM, Eoghan Murray wrote:
> 8.4: 314ms: http://explain.depesz.com/s/GkX
> 9.1: 10,059ms :http://explain.depesz.com/s/txn
> 9.1 with setting `enable_material = off`: 1,635ms
> http://explain.depesz.com/s/gIu
I think the problem is it's using a merge join, with a sort
I'm upgrading from 8.4 to 9.1 and experiencing a performance degradation on
a key query with 2 views and 2 tables.
Old server "PostgreSQL 8.4.10 on i686-redhat-linux-gnu, compiled by GCC gcc
(GCC) 4.1.2 20080704 (Red Hat 4.1.2-51), 32-bit"
New server "PostgreSQL 9.1.4 on x86_64-unknown-linux-gnu,
Hi Fellows
I have a question regarding PostgreSQL 9.1 indexing.
I am having a table and want to create a index for a column and I want to
store the data with time zone for that column. The questions are:
1. Can I create a index for a column which store time stamp with time zone.
If can is there
If someone is interested with the current strategy, I am using for
this, see this Ruby-based repo
https://github.com/stanislaw/truncate-vs-count for both MySQL and
PostgreSQL.
MySQL: the fastest strategy for cleaning databases is truncation with
following modifications:
1) We check is table is not
Version.
PostgreSQL 9.1.2 on x86_64-unknown-linux-gnu, compiled by gcc (GCC) 4.5.2,
64-bit
Server.
Server: RX800 S2 (8 x Xeon 7040 3GHz dual-core processors, 32GB memory
O/S: SLES11 SP1 64-bit
Scenario.
Legacy application with bespoke but very efficient interface to its persistent
Dear @,
Is there any tool or some sort of script available, for PostgreSQL, which
can be used to measure scalability of an application's database. Or is
there any guideline on how to do this.
I am a bit confused about the concept of measuring scalability of an
application's database.
How is t
great thanks for the help and explanation, I will start logging the
information you mentioned and do some analysis.
On Tue, Jul 10, 2012 at 10:46 AM, Craig Ringer wrote:
> On 07/10/2012 10:25 AM, Yan Chunlu wrote:
>
> I didn't set log_min_duration_statement in the postgresql.conf, but execute
the transaction part is wired, I have filtered BEGIN and COMMIT from a one
day log by using:
cat /usr/local/pgsql/data/pg_log/Saturday.log |grep -E "BEGIN|COMMIT"
>trans.txt
and pasted it to gist(only three BEGIN and many COMMIT):
https://gist.github.com/3080600
I didn't set log_min_duration_sta
Hi Mark,
I work for the division at LSI that supports the Nytro WarpDrive and can
confirm that these support poweroff safety (data is persistent in the event
of an abrupt loss of power). The Nytro WarpDrive has onboard capacitance to
sync intermediate ram buffers to flash, and after powerloss the
21 matches
Mail list logo
