Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
×
AMD Open Source Upgrades

AMD Forces a LibreOffice Speed Boost With GPU Acceleration 144

New submitter samtuke 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, about ¼ second vs. 2minutes, 21 seconds. Those measurements specifically come from the ground-water use sample from this set of Libre Office spreadsheets.
This discussion has been archived. No new comments can be posted.

AMD Forces a LibreOffice Speed Boost With GPU Acceleration

Comments Filter:
  • Not the right tool (Score:3, Interesting)

    by Cigaes ( 714444 ) on Saturday July 25, 2015 @09:37AM (#50180623) Homepage
    I wonder if a spreadsheet is really the right tool for computations that take several dozens of seconds on modern hardware, even without GPU acceleration. I am inclined to think it is not.
    • by Anonymous Coward on Saturday July 25, 2015 @09:44AM (#50180653)

      It can be. 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.

      • by Anonymous Coward on Saturday July 25, 2015 @12:04PM (#50181111)

        When the only tool you have is a spreadsheet, there is no place to sit because...

        ...everything looks like a table!

      • by tlhIngan ( 30335 )

        It can be. 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

    • by Daemonik ( 171801 ) on Saturday July 25, 2015 @09:45AM (#50180661) Homepage
      People use the tools they are familiar with. There are plenty of business types who are goddamn magic wizards with a spreadsheet who completely freeze up at the thought of putting a database together. I've seen spreadsheets clicking over into the 3-400mb range that have been used for years in organizations and you know it could be managed much more efficiently, yet people resist because it's easier for them to make quick modifications than passing along requests to a database admin.
    • by Mr D from 63 ( 3395377 ) on Saturday July 25, 2015 @10:15AM (#50180771)

      I wonder if a spreadsheet is really the right tool for computations that take several dozens of seconds on modern hardware, even without GPU acceleration. I am inclined to think it is not.

      It depends on the nature of the data and the calculation itself. If it is a relatively small data set and does not require relational tables, but a very complicated set of equations, then a spreadsheet might be a reasonable choice vs a database.

    • I wonder if a spreadsheet is really the right tool for computations that take several dozens of seconds on modern hardware, even without GPU acceleration. I am inclined to think it is not.

      No, it isn't but many accountants and business controllers are using spreadsheets, some of them also learn SQL, but that isn't really all that much better for financial calculations (though better as a database which they also use spreadsheets for).

    • by lorinc ( 2470890 )

      Exactly my thoughts also. Intensive computation and using a spreadsheet? You're doing it wrong.

      • by Anonymous Coward

        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

      • The fact of the matter is that computers have gotten more powerful where this sort of number crunching is no longer deemed "intensive" per the summary... A couple seconds after all versus many minutes per calculation.
    • A spreadsheet is easier to conceptualize, organize and manipulate than a database for most non-IT professionals and users, at the cost of higher risk on the data.

    • by gordo3000 ( 785698 ) on Saturday July 25, 2015 @12:02PM (#50181103)

      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.

      I've been at places that have tried to replace excel as the interaction layer. The problem is, for all its problems, most coders cannot hack together, on their own, a better GUI that is as performant or easily interacted with. Sometimes it isn't the data analysis layer (which if at all possible, we like to farm off somewhere else for perofrmance), but everything else that makes the spreadsheet far superior. And of course, I can modify and adapt someone else's work far faster than anyone using code. On a regular basis I can build up a complete tool in excel 10-20x faster than any coder can write me something outside of it. And most of the time a 95% correct answer in 1 hour is far more useful than a 100% correct answer in 3 days.

      Now saying that, once the office ribbon started, that was the beginning of the end. Slowly the interface is getting too clunky to waste my time with when it was the simplest things I required. Now I try to do a lot of my work in a proper coding language and write out files I can parse quickly in vba and display in excel.

    • by kevmeister ( 979231 ) on Saturday July 25, 2015 @01:47PM (#50181539) Homepage

      It's really amazing what you can do in a spreadsheet.

      Several years ago I was involved with management of optical wavelength switching gear (DWDM) in conjunction with a large, national telcom. They had some very well designed tools with very nice GUIs to allow things like building an optical path. Things that require managing complex database and doing a lot of checking on availability of resources and validity of the circuit.

      It was all written in Excel!

      I was amazed at it all. Nothing looked at all like a spreadsheet. and it actually worked and seemed pretty maintainable. I'm sure that they would have been delighted to see this sort of things as the one issue was the time it took to update the screen when certain changes were made (re-calculation).

    • by ceoyoyo ( 59147 )

      The idea of a spreadsheet that needs GPU acceleration is alarming.

  • Wrong tool (Score:5, Informative)

    by HuguesT ( 84078 ) on Saturday July 25, 2015 @10:42AM (#50180861)

    This is good of course, however, whenever I see a spreadsheet program used for any serious computation, I cringe. There are far better tools out there if you require real number crunching. Think Python + Panda for instance, or R, or Matlab if you are really into commercial programs, otherwise a nice interactive web page will usually do the trick. For accounting use a real accounting program, there are plenty out there. Spreadsheet programs are the lowest common denominator that allow the sharing of table-like information, but almost universally they are the wrong tool for the job. Just in the last week, I have seen spreadsheets used for a program logic workflow, a timetable, a university course schedule, to compute an FFT, to exchange student marks, to discuss a budget (with lots of deletions and remarks), and even for a presentation. In each and every case a more suitable, open-source, freely available, multi-platform application exists.

    Of course this is software that people know, so usually we have to deal with it. As a rule I accept to work with other people's spreadsheets, but I usually refuse to create one ex-nihilo, unless there is a compelling reason to. For instance I teach a course on optimisation, and I do show how the solver in Excel / {Libre,Open}Office works. I have also on occasion shown people how to use a pivot table (never use those if you can help it).

    The most severe problem I see with spreadsheet is that they have their use but they are fragile. It is too easy to load an extensive table into them and inadvertently modify just one cell, potentially undoing a lot of work. This is easy to detect if your spreadsheet is small, but if it span multiple tabs and an ungodly number of rows, you will not detect your error. Of course the format of these spreadsheet is obscure, and version control is typically not supported.

    Personally the worst I have seen was one spreadsheet used for the accounting of 90+ separate research projects, spanning 30,000 cells. The accountant in charge of it was the person most attentive to detail I have ever seen. She was careful and the only person using it, which made her indispensable. We put in place a year-long plan for her retirement, involving scrapping her spreadsheet, entirely replacing it with a direct interface with SAP via a php-based web page. It was many months in the making, of course this was not a trivial project but we've pulled it off. In the process we discovered a huge number of accounting errors thanks to it, typically invoices that were never billed, to the tunes of nearly one million dollars. It took us several months to correct them.

    The morals of this is never, ever use spreadsheets program for non-trivial work.

    • Re:Wrong tool (Score:5, Insightful)

      by Daemonik ( 171801 ) on Saturday July 25, 2015 @11:19AM (#50180963) Homepage

      ...Just in the last week, I have seen spreadsheets used for a program logic workflow, a timetable, a university course schedule, to compute an FFT, to exchange student marks, to discuss a budget (with lots of deletions and remarks), and even for a presentation. In each and every case a more suitable, open-source, freely available, multi-platform application exists.

      You've just stated the reason people use spreadsheets right there. One multi-purpose program vs umpteen specialist programs, each with their own UI quirks that have to be learned to make the most use of the programs. Why bother when a good old spreadsheet will work.

    • by trawg ( 308495 )

      The morals of this is never, ever use spreadsheets program for non-trivial work.

      This is only really a valid conclusion if you compare it against the lost billing rate of other solutions though. I have seen organisations that would happily allow billing stuff to fall through the cracks with specialised software simply because it was easier than trying to fight the software for certain situations.

      I can imagine that someone with Excel might end up saving more money for that reason, although I certainly agree the average complicated spreadsheet probably has a lot of errors.

    • n the process we discovered a huge number of accounting errors thanks to it, typically invoices that were never billed, to the tunes of nearly one million dollars. It took us several months to correct them.

      About 20 years ago I did some contract work for a hospital whose accounting group did all of their day-to-day work with Quattro Pro, then a nightly process batched all of the spreadsheet work into the actual accounting system that ran on a System/390. The spreadsheet was useful for the bookkeepers an
  • not just AMD (Score:3, Insightful)

    by Gravis Zero ( 934156 ) on Saturday July 25, 2015 @10:55AM (#50180899)

    AMD engineers have contributed OpenCL code which is an open standard that can run on many different accelerators (some not even GPUs [parallella.org]). this is distinctly different from CUDA which only works with Nvidia stuff.

    • Re: (Score:2, Insightful)

      by Blue Stone ( 582566 )

      Nvidia is really starting to piss me off with their proprietary shit like this, Gsync and their 'nVidia hair' bollocks for games.

  • Where is the open source version of OneNote? It's the only thing holding me to windows.
  • by XB-70 ( 812342 ) on Saturday July 25, 2015 @12:22PM (#50181173)
    I love LibreOffice and use it all the time... with one caveat: there appears to be little or no development going on with Base.

    I may be completely wrong but no features have been added in ages, no code updates etc. etc.

    Does anyone know what's going on?

    Also, would Base benefit from this GPU enhancement?

  • by FithisUX ( 855293 ) on Saturday July 25, 2015 @12:37PM (#50181219)
    While the intended workflow for data crunching on the desktop is typically served by R/Python/Julia among others, there are times you have to do some processing for a huge amount of data for a spreadsheet you have open in front of you. This is where AMD/LibreOffice will shine and this is a good motive to buy AMD and LibreOffice.
  • Comment removed based on user account deletion

"Protozoa are small, and bacteria are small, but viruses are smaller than the both put together."

Working...