-
Notifications
You must be signed in to change notification settings - Fork 6
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
Decide if moving to MonetDB before Beta. #482
Comments
I think we should at least try. Roll on the AG data with SSD and see how it flies! :-) |
That functionality could be good for custom summarisers. I've also tried the python module that is vice versa - monet in the python process. It was super speedy, but I have no idea how it would work with a multiprocess web server. |
My current list of concerns that need checking:
|
Quick update: I am working this demo instance towards dynamic filterbanking - I've created a new query method on the server that supports SQL aggregations and returns ArrayBuffers that this will use. |
The instance at http://104.199.5.137/ has been updated - the genome browser is now completely DB driven. There are a few rough edges still to work on (e.g. query cancelling) but in general I am very happy with this approach so far. |
PR #488 is ready! I'll take silence as a rousing endorsement of switching to Monet ;) Happy to hear any concerns though. |
JFDI :-) On Thursday, 8 September 2016, Ben Jeffery notifications@github.com wrote:
Alistair Miles |
We're close to beta where we will be polishing and having public releases of Panoptes 2.0, so we'd like to have a hiatus on large feature work. We probably have time to switch to MonetDB as the last big change. Do we want to do this? I have rebased the MonetDB branch (https://github.com/cggh/panoptes/tree/monet_rebased) and will load up AG on it for some testing on an SSD based machine.
My personal opinion is that if no show-stoppers are found then we should go ahead. It would potentially let us avoid pre-calculating filter banks, opening the door to parameterised filterbanks, such as filtered variant density.
Comments welcome!
The text was updated successfully, but these errors were encountered: