On Wed, Mar 3, 2010 at 4:45 PM, Josh Berkus wrote:
>> I feel like I've seen these way-too-high row estimates in some other
>> postings to -performance, but I'm not sure if it was the same issue.
>> You don't by chance have a RTC? I don't think it's likely fixed in 9.0
>> but it would be interestin
> I feel like I've seen these way-too-high row estimates in some other
> postings to -performance, but I'm not sure if it was the same issue.
> You don't by chance have a RTC? I don't think it's likely fixed in 9.0
> but it would be interesting to investigate.
Yeah, I can generate one pretty easi
On Fri, Feb 26, 2010 at 6:24 PM, Tory M Blue wrote:
> Ya my boxes are pretty well stacked, but a question. How does one get
> the memory usage of a query. You state to look at explain analyze but
> this gives timing and costs, but is one of the numbers memory or do I
> have to take values and do s
On Wed, Mar 3, 2010 at 4:53 AM, Hannu Krosing wrote:
> On Wed, 2010-03-03 at 10:41 +0100, Yeb Havinga wrote:
>> Scott Marlowe wrote:
>> > On Tue, Mar 2, 2010 at 1:51 PM, Yeb Havinga wrote:
>> >
>> >> With 24 drives it'll probably be the controller that is the limiting
>> >> factor
>> >> of bandw
On Sun, Feb 28, 2010 at 3:19 PM, Josh Berkus wrote:
> All,
>
> I'm seeing in a production database two problems with query rowcount
> estimation:
>
> (1) Estimates for the number of rows in an outer join do not take into
> account any constraint exclusion (CE) in operation.
>
> (2) Row estimates d
On Thu, Feb 25, 2010 at 6:29 PM, Yu-Ju Hong wrote:
> Thanks for the reply.
>
> On Thu, Feb 25, 2010 at 5:48 PM, Greg Smith wrote:
>>
>> Yu-Ju Hong wrote:
>>>
>>> 2. Moreover, the disk utilization was high and the "await" time from
>>> iostat is around 500 ms. Could disk I/O limit the overall thro
Greg Smith wrote:
> Bruce Momjian wrote:
>> I always assumed SCSI disks had a write-through cache and therefore
>> didn't need a drive cache flush comment.
Some do. SCSI disks have write-back caches.
Some have both(!) - a write-back cache but the user can explicitly
send write-through requests.
Francisco Reyes wrote:
Yeb Havinga writes:
controllers. Also, I am not sure if it is wise to put the WAL on the
same logical disk as the indexes,
If I only have two controllers would it then be better to put WAL on
the first along with all the data and the indexes on the external?
Specially
Francisco Reyes wrote:
Who are you using for SAS?
One thing I like about 3ware is their management utility works under
both FreeBSD and Linux well.
3ware has turned into a division within LSI now, so I have my doubts
about their long-term viability as a separate product as well.
LSI used to
Yeb Havinga writes:
controllers. Also, I am not sure if it is wise to put the WAL on the
same logical disk as the indexes,
If I only have two controllers would it then be better to put WAL on the
first along with all the data and the indexes on the external? Specially
since the external encl
With 24 drives it'll probably be the controller that is the limiting
factor of bandwidth. Our HP SAN controller with 28 15K drives delivers
170MB/s at maximum with raid 0 and about 155MB/s with raid 1+0.
I get about 150-200 MB/s on a linux software RAID of 3 cheap Samsung
SATA 1TB dr
Francisco Reyes wrote:
Going with a 3Ware SAS controller.
Have some external enclosures with 16 15Krpm drives. They are older
15K rpms, but they should be good enough.
Since the 15K rpms usually have better Transanctions per second I will
put WAL and indexes in the external enclosure.
It
Scott Marlowe wrote:
On Tue, Mar 2, 2010 at 1:51 PM, Yeb Havinga wrote:
With 24 drives it'll probably be the controller that is the limiting factor
of bandwidth. Our HP SAN controller with 28 15K drives delivers 170MB/s at
maximum with raid 0 and about 155MB/s with raid 1+0. So I'd go for th
Greg Smith wrote:
Yeb Havinga wrote:
With 24 drives it'll probably be the controller that is the limiting
factor of bandwidth. Our HP SAN controller with 28 15K drives
delivers 170MB/s at maximum with raid 0 and about 155MB/s with raid 1+0.
You should be able to clear 1GB/s on sequential rea
14 matches
Mail list logo