<br><br><div class="gmail_quote">2011/9/14 Michał Piotrowski <span dir="ltr"><<a href="mailto:mkkp4x4@gmail.com">mkkp4x4@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Exactly. F15, PostgreSQL 9.0 and just service file from PostgreSQL<br>
9.1. Root filesystem and database are on SSD and Ext4.<br><br></blockquote><div><br>Okay... brace yourself.<br><br>I just ran this test on my non-SSD ext4 based F15 system and I get the opposite result on start...repeatably. On my system the systemd based start up in the admittedly simple service postgresql start testing is consistently faster by about a second. And just as interesting... my sysinit times are slower than yours, that's a real head scratcher for me. If my db test was less overall work to init for some reason I'd expect my numbers to be faster than yourse in both cases. I have no off the top of my head theory that could explain that except that your low level disk i/o is significantly different than mine. <br>
<br>Both variants of "service postgresql stop" is within a 1/10 of a second in my testing<br><br>I can give you the screen log captures for my tests if you desire to review
my actions but here here is the summary for my simple timing test: And admittedly I'm using a simply initiated postgres db. It could be that your real world database initialization workload is more intensive than my test and the disk i/o is now a limiting factor in a different way. <br>
<br>And of course my numbers do not discount what your seeing as my test is as anecdotal as your is. Your numbers may still be indicative of a more nuanced problem that can be resolved and its good to have your numbers as a starting point for a discussion around understanding optimization issues (like disk i/o). We just can't jump to conclusions about why you are seeing what your are seeing. I hope my numbers serve as a cautionary reminder to those others on this list that benchmarking disk io intensive tasks can be very complex and very system dependent. Certain other people in this discussion are being overly bombastic and seem to have forgotten this fact. I hope for all our sakes they can find a way to ratchet down the hyperbole and look at these sort of issues with a more clinical approach.<br>
<br><br><br>Okay so here's my summary of the quick tests. Please if you have an updated methodology for me to test, let me know. I'm willing to reuse a specially crafted pgsql database if you feel that will help you. Though I'd think we wan't to do that sort of deep dive comparison off list until we are ready to publish some summaries after we both feel comfortable with the test runs.<br>
<br>-jef <br><br>==========================================<br>SysVinit:<br>service postgresql status<br>postgresql.service - LSB: start and stop PostgreSQL server<br> Loaded: loaded (/etc/rc.d/init.d/postgresql)<br>
Active: inactive (dead)<br> CGroup: name=systemd:/system/postgresql.service<br><br><br>time service postgresql start<br>real 0m2.329s<br>user 0m0.028s<br>sys 0m0.046s<br><br><br>time service postgresql stop<br>
real 0m1.281s<br>user 0m0.035s<br>sys 0m0.096s<br><br>time service postgresql start<br>
real 0m2.242s<br>user 0m0.031s<br>sys 0m0.038s<br><br>time service postgresql stop<br>
real 0m1.235s<br>user 0m0.031s<br>sys 0m0.036s<br><br><br>=========================================<br>Systemd based:<br>status postgresql.service<br>postgresql.service - PostgreSQL database server<br> Loaded: loaded (/lib/systemd/system/postgresql.service)<br>
Active: inactive (dead)<br> CGroup: name=systemd:/system/postgresql.service<br><br> <br>time service postgresql start<br>real 0m1.141s<br>user 0m0.019s<br>sys 0m0.019s<br><br><br>time service postgresql stop<br>
real 0m1.146s<br>user 0m0.017s<br>sys 0m0.017s<br><br>
time service postgresql start<br>real 0m1.153s<br>user 0m0.016s<br>sys 0m0.019s<br><br>time service postgresql stop<br>real 0m1.144s<br>user 0m0.026s<br>sys 0m0.014s<br><br><br><br></div></div>