Hello, Iam confused on the different result I get when I compile userland on any machine better then a Dual Core 2.5Ghz 2GB RAM 160GB 7200 SATA / SATA ii On some machines I get a compile time of 45min, other machines 30min.. and the best of the case I get 30min. Sometimes that machine that takes 45min is far better hardware then a DualCore, in this case a QuadCore with SATA II/sata... Iam going to use these machines for database and Iam very concerned about these results Based on that I have this question: Is it normal that this varies so much? (Afterall a variation from 35min to 45min represents an increase of about %25 less efficiency!!) Is there a better way to benchmark the IO of a Hard Disk on OpenBSD , what should be the normal of a hard disk scanned as sd SATA/ SATA II with similar CPU/RAM as mentioned? Andres
Honestly, you'd do better asking that on a list dedicated to whatever database you're going to be running. In addition to helping you choose hardware to fit your needs, they'll totally pimp your configs, too.
On Sun, Feb 28, 2010 at 11:10 AM, Bret S. Lambert Thanks, it will still be interested then to know what the avergae userland compilation is on similar hardware? Also any standard way of benchmarking IO on openbsd? Thanks Andres
I would say it's probably bottlenecking on disk I/O based on what you're telling me. The quad core could have a shitty SATA chipset in it, causing poor I/O scores. If the times stop at 30 mins, it's probably the SATA controller that's reached its limit. Setting the controller to AHCI would give OpenBSD access to NCQ where available, but the driver would also have to be written to take advantage of this I would imagine. There would also have to *be* a driver for the controller, which wouldn't be needed if it's being run in legacy mode (IDE emulation essentially). If your hard drive comes up as wd0, it's set in Legacy mode. If it's sd0, it's in SATA/RAID/AHCI mode (dependant on manufacturer). -- Aaron Mason - Programmer, open source addict I've taken my software vows - for beta or for worse
On Sun, Feb 28, 2010 at 4:56 PM, Aaron Mason <firstname.lastname@example.org> Where one would find documentation that tells one which drivers support NCQ and which don't? Does the sili dirver support NCQ? sII3512 is supported by pciide, and not by the sili driver (drive gets detected wd0, it's a SATA 1), while sii3124 is handled by the sili driver, but the man page doesn't mention NCQ (this card supports it). Thanks.
None of us will likely be able to tell you why, you'll have to figure out what part is the bottleneck in your setup, assuming you have identical configurations software-wise. (softep? Partition layout? Version?) I don't know if building userland will take advantage of multiple CPUs, These results will be largely irrelevant for your database load. However, learning how to use the available tools to find the bottleneck The best way to benchmark the I/O will be to set up your database with some clients and run your workload. Otherwise, you'll spend your time finding the fastest disk subsystem, only to discover that wasn't your bottleneck anyway.
Hi! You didn't provide too many details. Based on that it could be any of the following: Different CPU (Intel vs. AMD, CPU generations, amount of CPU cache...) Different FSB Different memory setup or technology (integrated vs. on-board memory, controller single-channel vs. dual-channel vs. triple-channel, DDR vs. DDR2 vs. DDR3, ECC vs. noECC, buffered vs. unbuffered, memory speed or timings, ...) Different I/O or SATA controller Different chipset Misconfiguration (BIOS, OS, HDD, ...) Different HDD (platter density, RPM, HDD cache, manufacturer, ...) HDD layout (beginning vs. the end of disk) and probably a ton of others I didn't think of. How much, if at all, should any of these matter? No idea, you tell us :) Regards, Daniel.
You're not even telling us how you compile userland. How should we help ? is your obj in ram ? your tmp in ram ? are you building with make build ? make -j4 build ? something else ?
Hello, I dont have obj on ram, or /tmp . Iam using make build. Thank you Andres
Well, /tmp in RAM is going to make a big difference. And src/ is mostly parallel-clean. There's an unlikely race in perl, but otherwise make -jN build is going to go ~N times as fast on an n-core SMP system.
|Tony Luck||Re: Hardware Error Kernel Mini-Summit|
|James Bottomley||Re: [PATCH -mm 1/2] scsi: remove dma_is_consistent usage in 53c700|
|Andrey Borzenkov||Re: [possible regression] 2.6.22 reiserfs/libata sporadically hangs on resume from...|
|Linus Torvalds||Linux 2.6.26-rc6|
|Jeffrey V. Merkey||Re: Versioning file system|
|Morten Welinder||Re: [PATCH] use xrealloc in help.c|
|Junio C Hamano||Re: [PATCH 2/3] git-add--interactive: remove hunk coalescing|
|Alex Riesen||Re: git exclude patterns for directory|
|Giuseppe Bilotta||Re: [PATCH 4/4] gitweb: show notes in commit(diff) view|
|Jörg Sommer||[PATCH v2 08/13] Unify the lenght of $SHORT* and the commits in the TODO list|
|Andreas Sundstrom||Re: ~60k interrupts/sec for 1Gb/s iperf with r8169|
|David Miller||Re: [2.6.30-rc3] powerpc: compilation error of mace module|
|Denys Fedoryshchenko||Re: circular locking, mirred, 126.96.36.199|
|David Miller||Re: [PATCH -next] sfc: Use correct macro to set event bitfield|
|Wu Fengguang||Re: [PATCH] dm9601: handle corrupt mac address|
|Linux Kernel Mailing List||V4L/DVB: tm6000: add special usb request to quit i2c tuner transfer|
|Linux Kernel Mailing List||OMAP: DSS2: SDI driver|
|Linux Kernel Mailing List||PCI: introduce pci_pcie_cap()|
|Linux Kernel Mailing List||m68k: amiga - Mouse platform device conversion|
|Linux Kernel Mailing List||drivers/acpi: use kasprintf|
|frantisek holop||Re: mount ffs as msdos, system hangs|
|Ted Bullock||Re: Proliant DL380 G3 cannot get on network|
|Úlfar M. E. Johnson||installing openbsd in xen|
|Eric Furman||Re: Defending OpenBSD Performance|
|Damien Miller||Re: Patching a SSH 'Weakness'|