2011/9/15 Michał Piotrowski <mkkp4x4@xxxxxxxxx>: > 2011/9/14 Tom Lane <tgl@xxxxxxxxxx>: >> 3. As root, do >> date --rfc-3339=ns ; systemctl start postgresql.service ; date --rfc-3339=ns > > with dropped cache > > date --rfc-3339=ns ; systemctl start postgresql.service ; date --rfc-3339=ns > 2011-09-15 08:44:40.348239703+02:00 > 2011-09-15 08:44:44.651134587+02:00 > > without dropped cache > date --rfc-3339=ns ; systemctl start postgresql.service ; date --rfc-3339=ns > 2011-09-15 08:45:38.388010217+02:00 > 2011-09-15 08:45:42.633229665+02:00 Note that those timings are not interesting -- you are comparing apples to watermelons. Got to take #4 into consideration for a useful reading. (Read Tom's original email to the end for an explanation -- the init script and service units exit on very peculiar conditions. So timing their wallclock is a waste of time.) >> 4. Note the time from the first "date" output to the "database system is >> ready to accept connections" message getting logged (in the appropriate >> file under /var/lib/pgsql/data/pg_log, if you haven't changed any other >> logging settings). Stop and restart a few times to get a good average. So, what are your timings following step 4? cheers, m -- martin.langhoff@xxxxxxxxx martin@xxxxxxxxxx -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
