SQL backend to handle big data

Registered by gordon chung

the collector and notification worker only works on a single thread... enabling collector to use multiple workers causes massive amount of deadlocks because of updating done to source/project/user/resource tables. these tables do nothing to help queries and only act as a bottleneck or point of deadlock when recording metering data. we should store raw Samples and not update anything... queries can be done against Sample with the same/better performance as current design.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
Obsolete
Series goal:
None
Implementation:
Unknown
Milestone target:
None
Completed by
gordon chung

Related branches

Sprints

Whiteboard

duplicate, i don't know how to delete this --gordc

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.