Displaying 3 results from an estimated 3 matches for "137752".
Did you mean:
13772
2008 Mar 06
4
Wrong message information reported shortly after delivery
Hi,
If an IMAP fetch is issued some "short" time after a message was delivered
with dovecot deliver then dovecot reports wrong (zero) values
for that new message. Afterward, it reports the information OK.
This causes problems to our IMAP client.
The problem is easily reproduced with a large message on a slow machine.
I'm using dovecot 1.0.10
Here's a sample trace:
1 uid fetch
2012 Aug 10
1
virtio-scsi <-> vhost multi lun/adapter performance results with 3.6-rc0
...bw (KB/s) : min= 0, max=46312, per=1.14%, avg=4531.55, stdev=11079.47
write: io=12,215MB, bw=83,812KB/s, iops=20,952, runt=149244msec
slat (usec): min=8, max=28,453, avg=129.91, stdev=289.11
clat (usec): min=2, max=5,791K, avg=1705.47, stdev=23195.36
bw (KB/s) : min= 0, max=137752, per=0.49%, avg=5818.54, stdev=22757.79
cpu : usr=3.25%, sys=88.14%, ctx=19889, majf=0, minf=1209
IO depths : 1=0.0%, 2=0.0%, 4=0.1%, 8=0.1%, 16=0.1%, 32=87.5%, >=64=12.5%
submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
complete : 0=0.0%,...
2012 Aug 10
1
virtio-scsi <-> vhost multi lun/adapter performance results with 3.6-rc0
...bw (KB/s) : min= 0, max=46312, per=1.14%, avg=4531.55, stdev=11079.47
write: io=12,215MB, bw=83,812KB/s, iops=20,952, runt=149244msec
slat (usec): min=8, max=28,453, avg=129.91, stdev=289.11
clat (usec): min=2, max=5,791K, avg=1705.47, stdev=23195.36
bw (KB/s) : min= 0, max=137752, per=0.49%, avg=5818.54, stdev=22757.79
cpu : usr=3.25%, sys=88.14%, ctx=19889, majf=0, minf=1209
IO depths : 1=0.0%, 2=0.0%, 4=0.1%, 8=0.1%, 16=0.1%, 32=87.5%, >=64=12.5%
submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
complete : 0=0.0%,...