search for: 235mb

Hello, I have question about the overhead in lapply. x is a list of 3000 lists. Each of the i (1<=i<=3000) list elements is pair of two elements: a string vector and a data frame x is roughly 235MB. > gc() ## > z <- system.time(y <- lapply(x,function(r){ system.time(serialize(r,NULL))['elapsed'] })) > sum(unlist(y)) 18.812 > z user system elapsed 494.144 0.041 494.247 So, the entire lapply takes ~26 times longer than the sum of the individual operations....

I recently got a new SSD (ocz vertex LE 50gb) It seems to work really well as a ZIL performance wise. My question is, how safe is it? I know it doesn''t have a supercap so lets'' say dataloss occurs....is it just dataloss or is it pool loss? also, does the fact that i have a UPS matter? the numbers i''m seeing are really nice....these are some nfs tar times before

Hi, I'm using Dovecot 2.2.9 to replicate my mailbox to a remote server. My mailbox on ServerA is 235Mb, but on ServerB it ends up being 358Mb. Does anyone know why this is? Shouldn't they be the same size? doveconf -n from ServerA: # 2.2.9: /usr/pkg/etc/dovecot/dovecot.conf # OS: NetBSD 5.2 cobalt auth_mechanisms = plain login doveadm_password = secret doveadm_port = 12345 first_valid_uid...

...ame environment like below. - Distro : CentOS 6.9 - Kernel : 4.12.9 - GlusterFS : 3.10.5 - tcmu-runner : 1.2.0 - iscsi-initiator-utils : 6.2.0.873 and these are results from test. 1st. FILEIO on FUSE mounted - 333MB/sec 2nd. glfs user backstore - 140MB/sec 3rd. FILEIO on FUSE mounted with tgtd - 235MB/sec 4th. glfs user backstore with tgtd - 220MB/sec 5th. FILEIO on FUSE mounted (iSER) - 643MB/sec 6th. glfs user backstore (iSER) - 149MB/sec 7th. FILEIO on FUSE mounted with tgtd (iSER) - 677MB/sec 8th. glfs user backstore with tgtd(iSER) - 535MB/sec Every tests were done with dd command. As sh...