On Thu, May 8, 2014 at 1:11 AM, Johann Spies wrote:
>
>
>>
>> So my questions:
>>>
>>> 1. Will the SSD's in this case be worth the cost?
>>> 2. What will the best way to utilize them in the system?
>>>
>>
>> The best way to utilize them would probably be to spend less on the CPU
>> and RAM and
On Thu, May 08, 2014 at 10:11:38AM +0200, Johann Spies wrote:
I understand your remark about the CPU in the light of my wrong assumption
earlier, but I do not understand your remark about the RAM. The fact that
temporary files of up to 250Gb are created at times during complex queries, is
to me
>
> Why do you even want to use JBOD?
>
Not for postgresql , but for distributed filesystems like hdfs/qfs (which
are supposed to work on JBOD) with hypertable on top (so the nvram would
help with the commits, since it is the biggest bottleneck when
writing(commits need to be saved to multiple ser
On 8 May 2014 10:11, Johann Spies wrote:
>
> Question: How do I dedicate a partition to indexes? Were do I configure
> PostgreSQL to write them in a particular area?
>
>
>
I just discovered TABLESPACE which answered my question.
Regards
Johann
--
Because experiencing your loyal love is better
On 6 May 2014 13:07, Michael Stone wrote:
> On Tue, May 06, 2014 at 11:13:42AM +0200, Johann Spies wrote:
>
>> Analysis or the SAR-logs showed that there were too much iowait in the
>> CPU's on
>> the old system which has a lower spec CPU than the ones considered for
>> the new
>> system.
>>
>
>
Hello,
here I am - the lonely user of JBOD :-) I use exactly what you describe below,
we have a couple of Dell Servers with battery backed H700 controllers. On one
we let the controller do a RAID10 on others I use the single disks (as you
describe in useless RAID0s).
What we do then is use th
On 6.5.2014 16:43, Dorian Hoxha wrote:
> And nvram is ram on hardware-raid controller that is not erased on
> reboot(battery) ?
Yes.
> Can this nvram be used also when the configuration is
> jbod(justabunchofdisks) or some kind of raid(0/1/5/6/10 etc) is
> required to use the nvram.
That proba
And nvram is ram on hardware-raid controller that is not erased on
reboot(battery) ?
Can this nvram be used also when the configuration is
jbod(justabunchofdisks) or some kind of raid(0/1/5/6/10 etc) is required to
use the nvram.
On Tue, May 6, 2014 at 1:24 PM, Michael Stone wrote:
> On Tue, May
On Tue, May 06, 2014 at 01:15:10PM +0200, Dorian Hoxha wrote:
Since the commitlog/WAL is sequential-write, does it mattert that much to put
it in ssd
No, assuming a good storage system with nvram write buffer.
Mike Stone
--
Sent via pgsql-performance mailing list (pgsql-performance@postgr
Since the commitlog/WAL is sequential-write, does it mattert that much to
put it in ssd ?(i understand that it matters to put it in separate
disk-subsystem so the write/read patterns don't interfere)
On Tue, May 6, 2014 at 1:07 PM, Michael Stone wrote:
> On Tue, May 06, 2014 at 11:13:42AM +0200,
On Tue, May 06, 2014 at 11:13:42AM +0200, Johann Spies wrote:
Analysis or the SAR-logs showed that there were too much iowait in the CPU's on
the old system which has a lower spec CPU than the ones considered for the new
system.
iowait means the cpu is doing nothing but waiting for data from th
I can suggest to have a disks' layout using at least two RAIDs:
1) RAID10 SSD (or 15kRPM HDD) SAS for O.S. and "pg_xlog" folder where PG
writes WAL files before checkpoint calls.
2) RAID10 using how many span is possible for the default DB folder.
Regards,
2014-05-06 11:13 GMT+02:00 Johann Spi
I am busy reading Gregory Smith' s PostgreSQL 9.0 High Performance and
when the book was written he seemed to me a bit sceptical about SSD's. I
suspect the reliability of the SSD's has improved significantly since then.
Our present server (128Gb RAM and 2.5 Tb disk space and 12 CPU cores -
RAID
13 matches
Mail list logo
