search for: 143mb

...e volume is different. When you renormalize the WAV to its original volume the file is still 100% original. My tests are the following. source file WAV. 1 hour 440HTZ tone. 600MB. volume at 100. FLAC file size is 184MB. volume at 75. FLAC file size is 166MB. volume at 50. FLAC file size is 143MB. volume at 25. FLAC file size is 109MB. volume at 5. FLAC file size is 96MB. From184MB to 96MB. As you can see from the full 100 normalize volume to the 5 normalize volume it is half the file size. So to put it. I think that you should have your compression of FLAC to also include a normali...

Folks, I've noticed poor performance using sftp. If anyone has any advice on how to improve performance, I'd like to hear it. Test simply involved transferring a single 143MB MP3 file using defaults for all the program configs. The opensshd 3.0.2p1 server is used in all tests. Software: openssh suite 3.0.2p1 psftp (putty sftp client) latest dev snapshot pscp (putty scp client) latest dev snapshot winscp 2.0 beta cygwin 1.3.6 windows xp Localhost (client/server on sam...

...2:57 4489] INFO (__init__:1094) SUSPEND shinfo 000fffff [2007-10-19 18:02:57 4489] DEBUG (__init__:1094) Written done [2007-10-19 18:02:57 4489] INFO (__init__:1094) delta 1231ms, dom0 24%, target 9%, sent 0Mb/s, dirtied 2Mb/s 101 pages 7: sent 101, skipped 0, delta 23ms, dom0 95%, target 0%, sent 143Mb/s, dirtied 143Mb/s 101 pages [2007-10-19 18:02:57 4489] INFO (__init__:1094) Total pages sent= 986073 (0.94x) [2007-10-19 18:02:57 4489] INFO (__init__:1094) (of which 0 were fixups) [2007-10-19 18:02:57 4489] INFO (__init__:1094) All memory is saved [2007-10-19 18:02:57 4489] INFO (__init__:1094)...

...Size contributed by __llvm_covmap sections: 1.02 GB \_ Just within clang: 340.48 MB - Size contributed by __llvm_prf_names sections: 327.46 MB \_ Just within clang: 106.76 MB => Space wasted within the clang binary: 447.24 MB Running an instrumented clang binary triggers a 143MB raw profile write which is slow even with an SSD. This problem is particularly bad for frontend-based coverage because it generates a lot of extra name data: however, the situation can also be improved for PGO instrumentation. Proposal -------- Place PGO name data and coverage data outside of obj...

...LVM library (libFindDebugInfo) that llvm-profdata could use. > - Size contributed by __llvm_prf_names sections: 327.46 MB > \_ Just within clang: 106.76 MB > > => Space wasted within the clang binary: 447.24 MB > > Running an instrumented clang binary triggers a 143MB raw profile write > which > is slow even with an SSD. This problem is particularly bad for > frontend-based > coverage because it generates a lot of extra name data: however, the > situation > can also be improved for PGO instrumentation. > > Proposal > -------- > >...

...hat llvm-profdata could use. > > >> - Size contributed by __llvm_prf_names sections: 327.46 MB >> \_ Just within clang: 106.76 MB >> >> => Space wasted within the clang binary: 447.24 MB >> >> Running an instrumented clang binary triggers a 143MB raw profile write >> which >> is slow even with an SSD. This problem is particularly bad for >> frontend-based >> coverage because it generates a lot of extra name data: however, the >> situation >> can also be improved for PGO instrumentation. >> >>...

...tions: 1.02 GB > \_ Just within clang: 340.48 MB > > - Size contributed by __llvm_prf_names sections: 327.46 MB > \_ Just within clang: 106.76 MB > > => Space wasted within the clang binary: 447.24 MB > > Running an instrumented clang binary triggers a 143MB raw profile write > which > is slow even with an SSD. This problem is particularly bad for > frontend-based > coverage because it generates a lot of extra name data: however, the > situation > can also be improved for PGO instrumentation. > I want to point out that this is a...

...;> >> >>> - Size contributed by __llvm_prf_names sections: 327.46 MB >>> \_ Just within clang: 106.76 MB >>> >>> => Space wasted within the clang binary: 447.24 MB >>> >>> Running an instrumented clang binary triggers a 143MB raw profile write >>> which >>> is slow even with an SSD. This problem is particularly bad for >>> frontend-based >>> coverage because it generates a lot of extra name data: however, the >>> situation >>> can also be improved for PGO instrumenta...

...85k data, 572k init) With 66MB of usable memory out of 256MB recovered and a reasonable 93% of memory usable for userspace instead of just 67%. I also see this on my 256MB DOM0: Memory: 146536k/6028224k available (6122k kernel code, 3932612k absent, 1949076k reserved, 4761k data, 576k init) Only 143MB out of 256MB allocated for DOM0 is usable for userspace. Regards, -- Tobias PGP: http://8ef7ddba.uguu.de _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users