Skip to main content

How to do an already doomed test

Read this blog MS Office 2007 versus Open Office 2.2 shootout. The test was already flawed from the beginning for the following reasons:


  • The author did not upload the original file which is probably a Excel 97 xsl file as a reference


  • Instead, two different formats were used: one from OpenOffice 2.0 beta sxw which is a compressed file and other a xml file from Microsoft Office 2003.


  • Since two different formats were used, the test is automatically void of meaning because of the lack of the original file.


  • Renaming the xml file to xsl like the author, I verified if it can be read with OpenOffice 2.2. It does not because the data is interpreted as xml which will exceed the limit of row in Calc application. Office Excel 2003 will render like a spreadsheet due to proprietary XML parser. However, Excel 2003 cannot read sxc nor OpendDocument Spreadsheet unless SUN's Open Document Format plugin is used.


  • The test is unrealistic in real world business because of the size (273 Mib of spreadsheet data). According to the author, the spreadsheet is actually a log file. One has to wonder why using a spreadsheet application to archive log.

Comments

Smooge said…
As horrible as it sounds.. I have regularly seen 100+ MB excel spreadsheets with log data and other stuff in it.

Remember to look at the problem from a Windows users perspective. You have large amounts of data you want tabulated, and you have a very limited amount of tools to do it with. You can import the file into word, but it wont be able to correlate all the events together. So you import it into excel and have a column for time, for type of events, and data. Tada, now you can use a tool you are familiar with to manipulate the log data. (and you can use things like normalization etc if you need statistics). Is it optimal.. no.. but it is a matter of what tools you know. [I mean how many perl/awk/python programs do exactly the same thing because each specific author knew what one tool to write it with.]

Popular posts from this blog

Running Sapphire Radeon RX 560 on Fedora 27 beta (follow up)

Following the previous blog and some investigation, it turned out the kernel package from Mystro256 COPR repository based on agd5f kernel branch (one of AMD developers) resolves the blank screen issue. That could trigger a problem for users having a new AMD graphic hardware so perhaps a warning should be written on the release. Perhaps having one of contributors be part of kernel team bringing these improvement until those patches arrive to the mainline kernel for a better user experience.

Past the issue, the desktop experience with Radeon RX 560 was tremendously improved compared to the retired GTX 460 v2. Gnome on Wayland on Fedora runs smooth showing how far the open source amdgpu driver went through compared to previous years. That was also the opportunity to run a vulkan based smoke test demo on RADV, which is a counterpart of glxgears.

Overall the card is excellent once missing software are installed.

Running Sapphire Pulse Radeon RX 560 4GB on Fedora 27 Beta

I bought a Sapphire PulseRadeon RX 560 4GB to replace the broken Nvidia GTX 460 v2 after a long years of service. It is then my first ever dedicated AMD based video-card for a desktop.

The boot sequence on Fedora 27 hit a problem: a plain blank screen suggesting the card is not yet supported. Looking at Phoronix website revealed one of possible requirement missed: LLVM 5.0 which is currently not available to Fedora repository save a failed built. I filed a bug report to address the issue. Hopefully that will land on time for the official release of Fedora 27.

Vulkan now fully functional on ASUS X550ZE

Running Fedora 28 Design Suite post beta shows a nice surprise: Vulkan with RADV is fully functional on both South Island (Hainan) and Sea Island (Kaveri) cards on ASUS X550ZE laptop. amdgpu driver is needed to enable the feat in combination of boot parameter (cik.amdgpu_support=1 cik.radeon_support=0 si.amdgpu_support=1 si.radeon_support=0)

Some minor issues need be to addressed like occasional glitches. Otherwise the performance is stable enough for dail use.