Libreoffice Hardware Acceleration

Jul 3, 2013 - GPU horsepower will be harnessed in rewrite of LibreOffice code. Of HSA in AMD's GPUs and APUs (accelerated processing units). L ast month, AMD demonstrated the big improvements in performance we will find in LibreOffice thanks to the built-in hardware acceleration. Znachki na paneli leksus rx330. Executing a standard. About Cr OS Linux.

New submitter writes: AMD processors get rated and reviewed based on performance. It is in our self-interest to make things work really, really fast on AMD hardware.

AMD engineers contribute to LibreOffice, for good reason. Think about what happens behind a spreadsheet calculation. There can be a huge amount of math. Writing software to take advantage of a Graphics Processing Unit (GPU) for general purpose computing is non-trivial.

We know how to do it. AMD engineers wrote OpenCL kernels, and contributed them to the open source code base. Turning on the OpenCL option to enable GPU Compute resulted in a 500X+ speedup,.

Those measurements specifically come from the ground-water use sample from. Don't generalize to use cases you don't know, especially when people with no real programming skills are concerned. I honestly don't know any other software that is both as flexible and accessible as spreadsheets when it comes to doing computations on heaps of (mostly irregular) data. Even for people WITH programming skill, a spreadsheet is often faster when you need stuff done. When working with hardware, there are often pesky register settings that need to be configured just right - a spreadsheet. OK, so what do you want to do? Say that a large part of the workforce should sit idle or go back to school just because they didn't learn the optimal language for this specific problem?

Spreadsheets are typically used by non-programmers to perform calculations that are cumbersome or impractical to do manually. Or should they just offload the job to a programmer?

They can probably put together a spreadsheet in half the time it takes them to write a half-assed and partially incorrect specification for the progr. Really depends on use case. Our spreadsheets (finance, derivatives) can get damn big, but there are 3 reasons they persist: ease of modification, speed of the interface, and easy integration with powerful analytics libraries we use.

Now I have functioned in a python based environment before, and that had some huge benefits (especially when working on tick level data, or data that was just a pain to manage in VBA until I got output down to a reasonably visualizable size), and I regularly push for trade level data and details to be put off into a SQL database as it is pretty easy to write flexible queries to get what I want out. But visualizing data, interacting with historic data (user forms for display), generally integrating with many other financial libraries (bloomberg and reuters for realtime, internal quant libraries for complex calculations), and having a fast interface out of the box is amazing.