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

Explore alternative ways to handling the .dag file cytoscape uses #49

Open
iamh2o opened this issue Jul 12, 2024 · 0 comments
Open

Explore alternative ways to handling the .dag file cytoscape uses #49

iamh2o opened this issue Jul 12, 2024 · 0 comments

Comments

@iamh2o
Copy link
Contributor

iamh2o commented Jul 12, 2024

I have two ideas come to mind.

  1. Write the .dag file to a memory based file, which should greatle improve read/write times. Only noticeable on large datasets I imagine.

    • This should be easy given rclone. I'll test next time I have a giant dataset to work with.
  2. Can the .dag file be skipped entirely? Specically, can the flat file be skipped, and can the data be streamed from the database directly to the cytoscape client?

    • I feel like the answer is yes, but also, I'm still debugging a fair amount, and having the flat file to poke around in is helpful.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant