Laying the Database Foundation
This blueprints outlines the necessary steps to ensure that Wintermute's database framework is properly configured to be used with the rest of the system.
Blueprint information
- Status:
- Started
- Approver:
- Wintermute Developers
- Priority:
- High
- Drafter:
- Jacky Alciné
- Direction:
- Approved
- Assignee:
- Wintermute Developers
- Definition:
- Approved
- Series goal:
- Accepted for trunk
- Implementation:
-
Slow progress
- Milestone target:
-
1.0a
- Started by
- Jacky Alciné
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Each neuron can be stored small or large, it does not matter
neurons are inside a network, so they have input and output, and a relation to a neuron
Now those with minor experience would say, you cannot store it all, especially when we are building a huge network inside a database, however we can queue storage and limit storage operations by collecting multiple and store them per interval or queue size.
Maybe mysql is not the best server for this... I would prefer to use one that can make use of multiple CPU cores.
In the end a DBMS is file storage, if you can afford a little uncertainty, all storage operations can simply be written to CSV
So whatever the grand design of things may become, do not worry about IO performance.
