Task #441

Refactor raw logger to log to database

Added by Espen Solbu about 6 years ago. Updated about 6 years ago.

Status:NewStart date:05/13/2012
Priority:NormalDue date:
Assignee:Android Dashboard Developers% Done:

0%

Category:-Spent time:-
Target version:2.5 Maintenance

Description

Needed to be able to support timestamping of a frame while still supporting raw files

table should look like this

ModelId timestamp (ms resolution) frameType entireFrame

I have not yet decided if this should be a inMemory database, or file based database, might need file based to prevent memory from running out


Subtasks

Task #442: Export raw log to fileNewAndroid Dashboard Developers

History

#1 Updated by Espen Solbu about 6 years ago

  • Description updated (diff)

#2 Updated by Espen Solbu about 6 years ago

  • Description updated (diff)

#3 Updated by Espen Solbu about 6 years ago

  • Description updated (diff)

#4 Updated by Hans Cappelle about 6 years ago

Espen Solbu wrote:

I have not yet decided if this should be a inMemory database, or file based database, might need file based to prevent memory from running out

Be careful since writing information (file/db) might slow down app. In memory is less critical but then indeed we might have an issue with the amount.

What is wrong with the logging that is performed today? Or how is it performed today? Haven't looked at that part yet.

#5 Updated by Espen Solbu about 6 years ago

I need to log raw frames together with timestamp, to better support playback of raw files.
(framerate is dependent on the content of the stream, with hub connectet, it approaces 120 fps, while without hub it is typically 30)

We would have to test this out of course. but using similar approach as the dataloggers (thread with queue and consumer) should work fairly well, and in my experience with sqlite, it is just as fast as logging to file (however that experience is on other platforms)

Also available in: Atom PDF