George McCollister wrote:
oprofile is showing that memset (via dopr) is using about 60% of the CPU. I
traced back further and noticed most of the usage was coming from
EncodeDateTime.
I'm not quite sure why oprofile is showing that memset is hogging so much CPU.
Regardless, I found way to eli
I'm trying to optimize postgres performance on a headless solid state
hardware platform (no fans or disks). I have the database stored on a
USB 2.0 flash drive (hdparm benchmarks reads at 10 MB/s). Performance is
limited by the 533Mhz CPU.
Hardware:
IXP425 XScale (big endian) 533Mhz 64MB RAM
USB 2
