Re: less than 2 sec for response - possible?

So does that mean Postgres is not capable to scan\aggregate less than 10
mln rows and deliver result in less than 2 seconds?

On 07/06/16 09:46, trafdev wrote:
> Well, our CPU\RAM configs are almost same...
>
> The difference is - you're fetching\grouping 8 times less rows than I:
>
> You scan 16.5 mln rows and fetch ~200k rows in 2 seconds and than spend
> 1.4 sec for aggregation
>
> I'm scanning 3.5 mln rows and fetching 1.5 mln rows (8 times more than
> you) in 1.8 seconds and then spending rest (2.3 seconds) for aggregation...
>
> So please try to extend dates range 8 times and repeat your test.
>
>
>
> On 07/06/16 08:27, Torsten Zuehlsdorff wrote:
>>
>> On 06.07.2016 17:06, trafdev wrote:
>>> Wondering what are your CPU\RAM characteristics?
>>
>> Intel Core i7-2600 Quad Core
>> 32 GB DDR3 RAM
>> 2x 3 TB SATA III HDD
>>
>> HDD is:
>> Model Family: Seagate Barracuda XT
>> Device Model: ST33000651AS
>> Firmware Version: CC45
>> User Capacity: 3,000,592,982,016 bytes [3.00 TB]
>> Sector Size: 512 bytes logical/physical
>> Rotation Rate: 7200 rpm
>> Form Factor: 3.5 inches
>> Device is: In smartctl database [for details use: -P show]
>> ATA Version is: ATA8-ACS T13/1699-D revision 4
>> SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
>>
>> RAM is for example:
>>
>> Handle 0x002D, DMI type 17, 28 bytes
>> Memory Device
>> Array Handle: 0x002A
>> Error Information Handle: No Error
>> Total Width: 64 bits
>> Data Width: 64 bits
>> Size: 8192 MB
>> Form Factor: DIMM
>> Set: None
>> Locator: DIMM0
>> Bank Locator: BANK0
>> Type: DDR3
>> Type Detail: Synchronous
>> Speed: 1333 MHz
>> Manufacturer: Undefined
>> Serial Number: 4430793
>> Asset Tag: AssetTagNum0
>> Part Number: CT102464BA160B.C16
>> Rank: 2
>>
>> OS is FreeBSD 10.3. Do you need more information?
>>
>> Greetings,
>> Torsten
>>