I didn't intend them for any sort of machine-based analysis. I developed the
patch when I was having a slow-down of my own and the existsing "-d all" data
didn't have enough data to find the problem.
In the example cited, a time stamp would quickly show whether an SQL statement
was taking a lon
don't think i like these timestamped logs. you'll need a machine to
parse them. the way to profile stuff is to use `darktable -d perf', in
this case it's `darktable -d perf -d lighttable'.
-jo
On Tue, Feb 19, 2013 at 4:48 PM, Kevin wrote:
> The recent discussion in dt-user "lighttable sluggish w
The recent discussion in dt-user "lighttable sluggish with collection based on
multiple tags" made me think that a small patch I developed some time ago
could be of use.
It just places the time since startup at the beginning of each line produced
by dt_print.
A "git diff" is attached.
Cheers,
