Public bug reported:
Currently FTS is only approximating results when any of the *Subject
groupings are used. This means that asking FTS for 20 most recent
subjects containing a can right now return anything between 1 and 60
different subjects all depending on the order of recent events.
The
** Branch linked: lp:~rainct/zeitgeist/collapse-uri
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/947835
Title:
FTS doesn't work properly with *Subject groupings
Status
Adding massif profiles where one is current FTS and the other does the
collapsing (using md5-hashes the uris, see RainCT's branch)
** Attachment added: massif.out.without_hashes
https://bugs.launchpad.net/zeitgeist/+bug/947835/+attachment/2821508/+files/massif.out.without_hashes
--
You
Although I didn't do real benchmarking, but I don't really much
difference in query times.
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/947835
Title:
FTS doesn't work
Disk space usage (with ~60k events):
- original: 77.8MB
- with hashes: 79.7MB
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/947835
Title:
FTS doesn't work properly with
All in all I think this is good to go, I'm not really sure whether to
trust the massif profiles (basically they are the same both with and
without hashes), because gnome-system-monitor shows something different,
but perhaps it's the sysmon that's not to be trusted. :)
** Changed in: zeitgeist
Review: Needs Fixing
Looks really good, a couple of comments:
8 +#include cassert
25 +assert (g_checksum_type_get_length (G_CHECKSUM_MD5) == 16);
We have glib for that (g_assert) ;)
Let's also turn all the magic 16s into a const / #define.
88 +#include glib/gchecksum.h
Let's hack all zeitgeist in c++
On Tue, Mar 6, 2012 at 11:27 AM, Michal Hruby
michal.hr...@canonical.comwrote:
All in all I think this is good to go, I'm not really sure whether to
trust the massif profiles (basically they are the same both with and
without hashes), because
Ian, could you attach your ~/.local/share/zeitgeist/activity.sql to this
bug, so we can investigate? (mark it as private before doing so)
** Changed in: zeitgeist (Ubuntu)
Status: New = Incomplete
** Also affects: zeitgeist
Importance: Undecided
Status: New
** Changed in:
Attached activity.sqlite.
** Visibility changed to: Private
** Attachment added: ~/.local/share/zeitgeist/activity.sqlite
https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/928324/+attachment/2823153/+files/activity.sqlite
--
You received this bug notification because you are a
@Seif - the disproportional number of uris compared to events seems to
be caused by U1 logging its uids in the subject origin field effectively
creating twice as many uris as events.
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed
revno: 413
committer: Michal Hruby michal@gmail.com
branch nick: zeitgeist
timestamp: Tue 2012-03-06 23:03:17 +0100
message:
Don't index ubuntuone's uids
modified:
extensions/fts++/indexer.cpp
--
lp:zeitgeist
@Michal - That would make sense; in a fresh installation, I notice this
doesn't happen, but after enabling U1, this issue occurs reliably.
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to the bug report.
13 matches
Mail list logo
