Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Database as source instead of TCP sockets (baking) #3

Closed
Zbysekz opened this issue Jun 18, 2020 · 4 comments
Closed

Database as source instead of TCP sockets (baking) #3

Zbysekz opened this issue Jun 18, 2020 · 4 comments
Assignees
Labels
enhancement New feature or request

Comments

@Zbysekz
Copy link
Collaborator

Zbysekz commented Jun 18, 2020

Rework of vis to use SQLite3 database.

@Zbysekz
Copy link
Collaborator Author

Zbysekz commented Jun 18, 2020

discussed in this thread
Separated here to keep topic clear.

@Zbysekz
Copy link
Collaborator Author

Zbysekz commented Jun 18, 2020

repliyng to @breznak from here

yes, but it's a bit smart. Stores only sparse synapses, also in binary format (possibly can even compress?).

So, I quick test: TM(2048cols, 32 cells per col), ran a couple of iterations of randomized SDR. tm.saveToFile("/tmp/tm.dump") results in ~1MB. Which would be much more reasonable. Could you try this on your workload?

I generated dumps for 1000 hotgym iterations and it has 1,54GB (compressed to zip leads to 525MB)
Amazing! I am surprised by the ease of use of such a serialization! 😮 👍

Since iterating and crunching of distal synapses in python can take more than 40sec per iteration i will store distal DUMP besides sqlite3 database and pandaVis will grab what it needs afterwards(by use of tm.connections.readFromFile(fileName).

Thanks for that advice :)

@Zbysekz Zbysekz self-assigned this Jun 18, 2020
@Zbysekz Zbysekz added the enhancement New feature or request label Jun 18, 2020
@Zbysekz Zbysekz pinned this issue Jun 18, 2020
@breznak
Copy link
Member

breznak commented Jun 18, 2020

Since iterating and crunching of distal synapses in python can take more than 40sec per iteration

ok, you have a 2nd use-case for this, I've already started some work in htm-community/htm.core#668
but haven't gotten to it lately. I'll be able to give it some time next week.

So the querying might get a bit faster.

@Zbysekz Zbysekz closed this as completed Jun 18, 2020
@Zbysekz Zbysekz reopened this Jun 18, 2020
@Zbysekz Zbysekz mentioned this issue Jun 22, 2020
@Zbysekz
Copy link
Collaborator Author

Zbysekz commented Jun 22, 2020

Finished

@Zbysekz Zbysekz closed this as completed Jun 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants