search for: runts

Benchmark shows small performance improvement on fusion io device. Before: seq-read : io=1,024MB, bw=19,982KB/s, iops=39,964, runt= 52475msec seq-write: io=1,024MB, bw=20,321KB/s, iops=40,641, runt= 51601msec rnd-read : io=1,024MB, bw=15,404KB/s, iops=30,808, runt= 68070msec rnd-write: io=1,024MB, bw=14,776KB/s, iops=29,552, runt= 70963msec After: seq-read : io=1,024MB, bw=20,343KB/s,

Benchmark shows small performance improvement on fusion io device. Before: seq-read : io=1,024MB, bw=19,982KB/s, iops=39,964, runt= 52475msec seq-write: io=1,024MB, bw=20,321KB/s, iops=40,641, runt= 51601msec rnd-read : io=1,024MB, bw=15,404KB/s, iops=30,808, runt= 68070msec rnd-write: io=1,024MB, bw=14,776KB/s, iops=29,552, runt= 70963msec After: seq-read : io=1,024MB, bw=20,343KB/s,

Hi all, I''m trying to include the ''runt'' gem (http://runt.rubyforge.org/) in my Rails project. I''ve tried a few ways of doing this. I''ve tried installing runt using ''gem install runt'' and then trying to do "require ''runt''" in my environment.rb, and I''ve also tried using the ''vendor

I am planning on using Runt to calculate recurring events. I calculate a Runt object in the view and use it to see if it includes a certain date, which is populates from the database, and display the info for that date if it is included. I have recurring events for every week, which was pretty easy to set up. I can just say: r = Runt::DIWeek.new(4) For a recurring event every Thursday, and

After sending this I realized that this was a Ruby not Rails issue - but the answer may be interesting for those who choose Marshal over Serialize. So, to close this off I don''t know why marshal.dump wasn''t ''dumping'' all attributes, but adding custom marshaling to PDate did the trick. ala, + def marshal_dump + dumped_obj = [date_precision, ajd,

Hi folks, The following are initial virtio-scsi + target vhost benchmark results using multiple target LUNs per vhost and multiple virtio PCI adapters to scale the total number of virtio-scsi LUNs into a single KVM guest. The test setup is currently using 4x SCSI LUNs per vhost WWPN, with 8x virtio PCI adapters for a total of 32x 500MB ramdisk LUNs into a single guest, along with each backend

Hi folks, The following are initial virtio-scsi + target vhost benchmark results using multiple target LUNs per vhost and multiple virtio PCI adapters to scale the total number of virtio-scsi LUNs into a single KVM guest. The test setup is currently using 4x SCSI LUNs per vhost WWPN, with 8x virtio PCI adapters for a total of 32x 500MB ramdisk LUNs into a single guest, along with each backend

Holding the vblk->lock across kick causes poor scalability in SMP guests. If one CPU is doing virtqueue kick and another CPU touches the vblk->lock it will have to spin until virtqueue kick completes. This patch reduces system% CPU utilization in SMP guests that are running multithreaded I/O-bound workloads. The improvements are small but show as iops and SMP are increased. Khoa Huynh

Holding the vblk->lock across kick causes poor scalability in SMP guests. If one CPU is doing virtqueue kick and another CPU touches the vblk->lock it will have to spin until virtqueue kick completes. This patch reduces system% CPU utilization in SMP guests that are running multithreaded I/O-bound workloads. The improvements are small but show as iops and SMP are increased. Khoa Huynh

Greetings, I first want to say that this problem is happening with the Runt gem. This may is likely an implementation issue between Marshal and Runt. While I''ve simultaneously filed this problem with Matt Lipper, I''m also hoping someone here can can guide me a little - either in implementation (usage of Marshal), or to aid me to fix Runt to support Marshal.

yup runned it. probably something wrong with my initrd filesystem. can you send me a directory listing of your initrd? and probably a sample linuxrc. if worse comes to worse, i'll probably load my usb and scsi modules in the initrd. i'm probably doing it all wrong. i'm trying to imitate the slackware10usb way of booting up. every driver built in the kernel, patch on the mounting root

I''m using the runt library [1] to do some temporal expression matching. I want to keep the expression in a binary field in my db. I figured that then in order to do the fixtures, I''d need to do some erb in the yaml file. So I came up with this: onetime: id: 1 name: One Time description: This event occurs only one time. timex: <%= REYear.new(7) & REMonth.new(24)

I''m working on a project that has event scheduling and I need to get date recurrence going on it. I found the Runt library which looks like it has pretty much everything handled, but I was wondering if there are any tutorials out there for using Runt with Rails, or better yet some helpers or a plugin for it. I tried searching through the mailing list archives, but searching is down

Out of necessity, a friend of mine and I have created a patch for syslinux to allow it to modify the mbr and partition table in windows. It adds a -m option to syslinux. If given, it will overwrite the MBR of the drive specified with the mbr.bin provided in syslinux, and if the bootable flag is not set on the partition being syslinuxed, it will set it. This was done to distribute with my USB

Dear all, I wanna create a GNU/Linux that it boots from USB. I don't any idea on that. Can you introduce me a doc that i can use it & i can solve my problem? Cheers, -- ------------------------- Mohsen Pahlevanzadeh email address : mohsen at pahlevanzadeh.org web site : http://pahlevanzadeh.org IRC IM : m_pahlevanzadeh yahoo IM : linuxorbsd ----------------------------

Hi, Jens & Rusty This version is rebased against linux-next which resolves the conflict with Paolo Bonzini's 'virtio-blk: allow toggling host cache between writeback and writethrough' patch. Patch 1/3 and 2/3 applies on linus's master as well. Since Rusty will pick up patch 3/3 so the changes to block core (adding blk_bio_map_sg()) will have a user. Jens, could you please

Hi, Jens & Rusty This version is rebased against linux-next which resolves the conflict with Paolo Bonzini's 'virtio-blk: allow toggling host cache between writeback and writethrough' patch. Patch 1/3 and 2/3 applies on linus's master as well. Since Rusty will pick up patch 3/3 so the changes to block core (adding blk_bio_map_sg()) will have a user. Jens, could you please

Hi, all Changes in v7: - Using vbr->flags to trace request type - Dropped unnecessary struct virtio_blk *vblk parameter - Reuse struct virtblk_req in bio done function - Added performance data on normal SATA device and the reason why make it optional Fio test shows bio-based IO path gives the following performance improvement: 1) Ramdisk device With bio-based IO path, sequential

Hi, all Changes in v7: - Using vbr->flags to trace request type - Dropped unnecessary struct virtio_blk *vblk parameter - Reuse struct virtblk_req in bio done function - Added performance data on normal SATA device and the reason why make it optional Fio test shows bio-based IO path gives the following performance improvement: 1) Ramdisk device With bio-based IO path, sequential

This patchset implements bio-based IO path for virito-blk to improve performance. Fio test shows bio-based IO path gives the following performance improvement: 1) Ramdisk device With bio-based IO path, sequential read/write, random read/write IOPS boost : 28%, 24%, 21%, 16% Latency improvement: 32%, 17%, 21%, 16% 2) Fusion IO device With bio-based IO path, sequential