[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Fkt-devel] performance issues in fxt
From: |
François Trahay |
Subject: |
[Fkt-devel] performance issues in fxt |
Date: |
Thu, 25 Aug 2011 17:19:53 +0200 |
User-agent: |
KMail/1.13.7 (Linux/3.0.0-1-amd64; KDE/4.6.5; x86_64; ; ) |
Dear all,
I'm using fxt in eztrace and I am experiencing some performance issues due to
the way fxt_next_ev reads traces.
From my experience, each call to fxt_next_ev take approx. 2µs. Since I need to
browse traces consisting of millions of events (and these are 'small' traces),
it becomes prohibitive.
Actually fxt_next_ev calls 'read' several times, leading to a large overhead.
I managed to modify it so it reads 4KB blocks (reducing the number of calls to
read and thus the total overhead) and the performance increases a lot: each
call to fxt_next_ev now cost approx 200ns.
My patch is only lightly tested and this method restricts fxt features:
fxt_rewind becomes unavailable (but, it could be possible to reimplement it)
and calls to fxt_next_ev isn't thread-safe anymore (but adding thread-safety
should'nt be too hard).
Once these issues solved, do you think it could be integrated to fxt ? An
option could be added at fxt initialization to enable/disable the feature.
François
patch_fxt
Description: Text Data
- [Fkt-devel] performance issues in fxt,
François Trahay <=
- Re: [Fkt-devel] performance issues in fxt, Samuel Thibault, 2011/08/25
- Re: [Fkt-devel] performance issues in fxt, François Trahay, 2011/08/25
- Re: [Fkt-devel] performance issues in fxt, Samuel Thibault, 2011/08/26
- Re: [Fkt-devel] performance issues in fxt, François Trahay, 2011/08/26
- Re: [Fkt-devel] performance issues in fxt, Vincent Danjean, 2011/08/26
- Re: [Fkt-devel] performance issues in fxt, François Trahay, 2011/08/26
- Re: [Fkt-devel] performance issues in fxt, Samuel Thibault, 2011/08/26