-
Notifications
You must be signed in to change notification settings - Fork 123
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
Runtime of Bonito compared to Guppy (CPU and GPU) #57
Comments
Hey @zmunro The goals of the two projects are slightly different. Guppy is the official production basecaller which is fully supported and documented, it’s also the most performant. Bonito is an open source research project that provides everything you need for training and basecalling. Bonito is primarily a GPU focused project however it sounds like you want Guppy for the speed and documentation. If you are interested in method development then please do check out the code and feel free to ask for further clarification where needed. |
@iiSeymour Thanks for the response! I am still a little confused. Could you confirm my understanding of the following:
|
I am thinking about integrating some interesting technology from this company Neural Magic who have an ML prediction engine that allows you to build CNNs that can run on CPUs and get the same performance as GPUs. |
Yes, you are correct. Guppy is, in general, faster than Bonito at basecalling and Bonito does utilize GPU(s) for basecalling. Neural Magic make some impressive claims so if you get any results I’d be interesting in hearing about that. If you are interested in fast CPU inference then you might want to keep an eye on #52. |
Bonito basecalling speeds are now inline with guppy. |
I am interested in using the Bonito basecaller, but I am finding much less documentation on it compared to Guppy unfortunately. Is anyone aware of how Bonito compares to Guppy in terms of speed?
Also, depending on its normal speed, can Bonito utilize a GPU during basecalling?
The text was updated successfully, but these errors were encountered: