search for: microseconds

...\ -device virtio-balloon-pci,id=balloon0,bus=pcie.10 { "execute" : "balloon", "arguments": { "value" : 1073672192 } } {"return": {}} {"timestamp": {"seconds": 1693272173, "microseconds": 88667}, \ "event": "BALLOON_CHANGE", "data": {"actual": 1073610752}} {"timestamp": {"seconds": 1693272174, "microseconds": 89704}, \ "event": "BALLOON_CHANGE", "data": {"actua...

...\ -device virtio-balloon-pci,id=balloon0,bus=pcie.10 { "execute" : "balloon", "arguments": { "value" : 1073672192 } } {"return": {}} {"timestamp": {"seconds": 1693272173, "microseconds": 88667}, \ "event": "BALLOON_CHANGE", "data": {"actual": 1073610752}} {"timestamp": {"seconds": 1693272174, "microseconds": 89704}, \ "event": "BALLOON_CHANGE", "data": {"actua...

...\ > -device virtio-balloon-pci,id=balloon0,bus=pcie.10 > > { "execute" : "balloon", "arguments": { "value" : 1073672192 } } > {"return": {}} > {"timestamp": {"seconds": 1693272173, "microseconds": 88667}, \ > "event": "BALLOON_CHANGE", "data": {"actual": 1073610752}} > {"timestamp": {"seconds": 1693272174, "microseconds": 89704}, \ > "event": "BALLOON_CHANGE", "data&q...

AGI's are resulting in unusual behaviors. Can someone please tell me if this is my inappropriate use of AGI's, inappropriate use of Time::HiRes, or a bug with *: I call this script twice: #!/usr/bin/perl use Time::HiRes qw( gettimeofday ); ($seconds, $microseconds) = gettimeofday; $hirestime = sprintf("%s","$seconds$microseconds"); print "SET VARIABLE HIRESTIMESTAMP $hirestime\n"; I run this script twice, once before a bunch of stuff, and once after, in order to perform a crude version of time measurement. However, the scrip...

...1072 4409.00 bw_pipe -Pipe bandwidth: 85.42 MB/sec +Pipe bandwidth: 989.19 MB/sec bw_unix -AF_UNIX sock stream bandwidth: 104.75 MB/sec +AF_UNIX sock stream bandwidth: 968.87 MB/sec lat_ctx -"size=0k ovr=3.15 -10 13.95 +"size=0k ovr=1.09 +10 0.94 lat_fcntl -Fcntl lock latency: 43.2246 microseconds +Fcntl lock latency: 5.4676 microseconds lat_fifo -FIFO latency: 32.4076 microseconds +FIFO latency: 3.3622 microseconds lat_fs -0k 1000 18563 31549 -1k 1000 6426 17887 -4k 1000 6583 17826 -10k 1000 3084 14989 +0k 1000 63666 92541 +1k 1000 241...

...uot;:"balloon","arguments":{"value":8589934592},"id":"libvirt-9"} 2013-03-22 21:13:45.528+0000: 23179: debug : qemuMonitorIOProcess:353 : QEMU_MONITOR_IO_PROCESS: mon=0x7f3d6c1789e0 buf={"timestamp": {"seconds": 1363986825, "microseconds": 528314}, "event": "BALLOON_CHANGE", "data": {"actual": 12883853312}} 2013-03-22 21:13:45.528+0000: 23179: debug : qemuMonitorJSONIOProcessLine:152 : Line [{"timestamp": {"seconds": 1363986825, "microseconds": 528314}, &quo...

Hello I have a string which contains microseconds, can anyone help on constructing this in to a time object, with the microseconds, that I can take to a ZOO file? Thanks Sean > UK[1,3] [1] "17:09:53.824" > UK[1,1] [1] "2007-12-11 00:00:00" > mydates <- paste( substr(UK[,1], 1, 10), UK[,3]) > mydates[1] [1]...

...rent Dell servers, one is Lenny kernel 2.6.26 asterisk 1.6.2.20, the second CentOS 2.6.18 asterisk 1.4.36 (Elastix). Both 64bits, no hardware involved, dahdi on both machines for meetme timing. Doing core show translation give on the Lenny server Translation times between formats (in microseconds) for one second of data Source Format (Rows) Destination Format (Columns) g723 gsm ulaw alaw g726aal2 adpcm slin lpc10 g729 speex ilbc g726 g722 siren7 siren14 slin16 g723 - - - - - - - - - - - - -...

...ems that the last digit of the 'sec' attribute sometimes seems to differ from the digits shown when printing the 'POSIXlt' object. You'll find a little SO post with some example code here: http://stackoverflow.com/questions/11725517/ambiguity-with-posixlt-representation-when-microseconds-are-included. In case you don't want to have a look at that, here's another short example: |opts<- options(digits.secs=6) x<- "2012-07-30 12:10:09.123123" posix<- as.POSIXlt(x, tz="Europe/Berlin") > posix [1] "2012-07-30 12:10:09.123122 Europe/...

...he behavior with a test that simply returns an existing object from the worker back to the main R session. library(parallel) library(microbenchmark) gcinfo(TRUE) cl <- makeCluster(1) (x <- microbenchmark(clusterEvalQ(cl, iris), times = 1000, unit = "us")) plot(x$time, ylab = "microseconds") head(x$time, n = 10) On Windows/MacOS, the test runs in 300-500 microseconds depending on hardware. A few of the 1000 runs are an order of magnitude slower but this can probably be attributed to garbage collection on the worker. On Linux, the first 5 or so executions run at comparable sp...

...s. Experiment 2] bw_mem benchmark 1. ./bw_mem 1000m wr dom0 output: 1048.58 3640.60 domU output: 1048.58 4719.32 2. ./bw_mem 1000m rd dom0 output: 1048.58 5780.56 domU output: 1048.58 6258.32 Experiment 3] lat_syscall benchmark 1. ./lat_syscall write dom0 output: Simple write: 1.9659 microseconds domU output : Simple write: 0.4256 microseconds 2. ./lat_syscall read dom0 output: Simple read: 1.9399 microseconds domU output : Simple read: 0.3764 microseconds 3. ./lat_syscall stat dom0 output: Simple stat:3.9667 microseconds domU output : Simple stat: 1.2711 microseconds I am not able...

Does R have support for microseconds in timestamps, e.g. when reading this in "Time","Include","Kind","Duration" 2011-04-01 14:20:36.368324,Y,U,1.03238296509 2011-04-01 14:20:35.342732,Y,C,0.0252721309662 2011-04-01 14:20:34.337209,Y,R,0.00522899627686 Thanks, Joel --------------------------...

Hi all, I need a periodic timer running at ideally at 125 microseconds and at least 500 microseconds. I''ve just found the VCPUOP_set_periodic_timer, however there is a comment saying "periods less than one millisecond may not be supported". I will be running on an x64 machine. Is this supported? If not, is there any alternate means of generatin...

...sockets on Linux could do with TCP_NODELAY -- without (status quo): How many network packets are generated with and without it? If there are many small writes and thus setting TCP_NODELAY causes many small packets to be sent, it might make more sense to set TCP_QUICKACK instead. I?aki > Unit: microseconds > expr min lq mean median uq max > clusterEvalQ(cl, iris) 1449.997 43991.99 43975.21 43997.1 44001.91 48027.83 > neval > 1000 > > exactly the same machine + R but with TCP_NODELAY enabled in R_SockConnect(): > > Unit: microse...

Dear list, When using as.POSIXlt with times measured down to microseconds the default format.POSIXlt seems to cause some possibly undesirable behaviour: According to the code in format.POSIXlt the maximum accuracy of printing fractional seconds is 1 microsecond, but if I do; options( digits.secs = 6 ) as.POSIXlt( 1.000002 , tz="", origin="1970-01-01&quot...

Hi, What exactly are the "tokens"? I thought each token allowed the sending of one byte, that tokens are stored in a bucket that can hold a max of "burst" tokens, and that this bucket is filled with tokens at "rate". But theory does not seem to explain the "tc -s .." output in the examples below. And I can''t figure out why or how... #tc qdisc

...s timeout_get_wait_time() (both in ioloop.c). The timeout is computed by subtracting the value returned by gettimeofday() from timeout->next_run, and it looks like in very rare cases the result in tv_r->tv_usec is 1000000uS (1 second). So, it seems that if gettimeofday() returns exactly 0 microseconds, and timeout->next_run has exactly 1000000 microseconds, the kevent() call will fail (1 in 1e12 chance?). I'm not entirely sure where timeout->next_run is computed, but looking at timeout_update_next(), it adjusts the seconds only if the microseconds are greater than 1000000:? (ioloo...

This should be of interest to us, asterisk buffs: http://www.linuxdevices.com/news/NS6761928882.html -- "We hold [...] that all men are created equal; that they are endowed [...] with certain inalienable rights; that among these are life, liberty, and the pursuit of happiness" -- Thomas Jefferson -------------- next part -------------- An HTML attachment was scrubbed... URL:

...------------------------------------- f1 <- function(pkg) pkg %in% loadedNamespaces() f2 <- function(pkg) !is.null(.getNamespace(pkg)) require(microbenchmark) pkg <- "foo"; (mbM <- microbenchmark(r1 <- f1(pkg), r2 <- f2(pkg))); stopifnot(identical(r1,r2)); r1 ## Unit: microseconds ## expr min lq mean median uq max neval cld ## r1 <- f1(pkg) 38.516 40.9790 42.35037 41.7245 42.4060 82.922 100 b ## r2 <- f2(pkg) 1.331 1.8285 2.13874 2.0855 2.3365 7.252 100 a ## [1] FALSE pkg <- "stats"; (mbM <- microbenchmark(...

...out (status quo): >> How many network packets are generated with and without it? If there >> are many small writes and thus setting TCP_NODELAY causes many small >> packets to be sent, it might make more sense to set TCP_QUICKACK >> instead. >> I?aki >>> Unit: microseconds >>> expr min lq mean median uq max >>> clusterEvalQ(cl, iris) 1449.997 43991.99 43975.21 43997.1 44001.91 48027.83 >>> neval >>> 1000 >>> exactly the same machine + R but with TCP_NODELAY enabled in R_Soc...