4 ms·
Relatively static is correct. The data you bring into blazingdb is normally brought in ready to be operated on with the understanding that it will not change o
by felipe_aramburu 10y ago
Relatively static is correct. The data you bring into blazingdb is normally brought in ready to be operated on with the understanding that it will not change on a regular basis. So there are many datasets that already exist, do not change, and are absolutely enormous that people want to analyze. GPUs allow us to quicky compress and decompress data to reduce file i/o bottleknecks, perform massive transformations much more quickly than on cpu, give us the computational capacity to find the best ways to optimize the layout of the information to take the most advantage of data skipping. The intention here is to provide you access to arbitrary large amounts of data with a horizontally scalable database solution that has orders of magnitude more computational capacity than a cpu based solution.
- tyingq 10y agoMight be good to get that "read+append only" message more upfront. Redshift has update, delete, etc, and you're making direct comparisons. You do push the "data warehouse" message, but it may not be clear that anything other than append would require reloading the entire database.
- felipe_aramburu 10y agoUpdate / Delete is forthcoming. We have a version of it working but have not pushed it yet because it is part of a broader set of changes that have not been made availble yet.