Comments for The Linux Bloke http://www.linuxbloke.com Who's the Biggest Geek on the Internet? Sat, 14 Aug 2010 23:47:27 +0000 hourly 1 http://wordpress.org/?v=3.0 Comment on The Difference Between Multithreaded and Multicore Programming by MEE SQA Blog » 2010 » August » 14 http://www.linuxbloke.com/2009/06/29/the-difference-between-multithreaded-and-multicore-programming/#comment-2485 MEE SQA Blog » 2010 » August » 14 Sat, 14 Aug 2010 23:47:27 +0000 http://www.linuxbloke.com/?p=245#comment-2485 [...] The Linux Bloke - The Difference between Multithreaded and Multicore Programming [...] [...] The Linux Bloke – The Difference between Multithreaded and Multicore Programming [...]

]]> Comment on Ever tried calling a win32ole (COM) object from Ruby’s DRb? by pete http://www.linuxbloke.com/2010/06/26/ever-tried-calling-a-win32ole-com-object-from-rubys-drb/#comment-2376 pete Mon, 28 Jun 2010 20:28:33 +0000 http://www.linuxbloke.com/?p=266#comment-2376 <a href="http://redmine.ruby-lang.org/issues/show/2618" rel="nofollow">A bug was filed</a> about Win32Ole being non-threadsafe in 1.9.1, and it has unfortunately not been fixed. 1.8.x and 1.9.2 don't look to be affected the same way though. I found a <a href="http://gist.github.com/407804" rel="nofollow">workaround</a> for this bug in 1.9.1, but I haven't used it in production so YMMV. A bug was filed about Win32Ole being non-threadsafe in 1.9.1, and it has unfortunately not been fixed. 1.8.x and 1.9.2 don’t look to be affected the same way though.

I found a workaround for this bug in 1.9.1, but I haven’t used it in production so YMMV.

]]> Comment on OpenOffice File Menu “Randomly” Pops Up on Ubuntu. by Mike http://www.linuxbloke.com/2010/01/10/openoffice-and-skype-conflicts-on-ubuntu-openoffice-file-menu-randomly-pops-up/#comment-2344 Mike Mon, 12 Apr 2010 03:10:27 +0000 http://www.linuxbloke.com/?p=252#comment-2344 I have the same problem where the File menu always pops up randomly in OpenOffice. I am using OpenOffice.org 3.0.1 in Ubuntu 9.04. I have solved this problem by removing Compiz (an OpenGL window and compositing manager) in the terminal as follows # sudo apt-get remove compiz compiz-core After I logout and login again to my Ubuntu workstation, the pop up problem is gone. Note that I got this idea from: http://forums.opensuse.org/get-help-here/applications/394412-problem-openoffice-file-menu-activates-itself.html Regards, Mike I have the same problem where the File menu always pops up randomly in OpenOffice. I am using OpenOffice.org 3.0.1 in Ubuntu 9.04. I have solved this problem by removing Compiz (an OpenGL window and compositing manager) in the terminal as follows

# sudo apt-get remove compiz compiz-core

After I logout and login again to my Ubuntu workstation, the pop up problem is gone. Note that I got this idea from:

http://forums.opensuse.org/get-help-here/applications/394412-problem-openoffice-file-menu-activates-itself.html

Regards,

Mike

]]> Comment on Using Ruby to Migrate Databases by Fred Mitchell http://www.linuxbloke.com/2008/08/09/using-ruby-to-migrate-databases/#comment-2340 Fred Mitchell Wed, 06 Jan 2010 18:02:54 +0000 http://www.linuxbloke.com/?p=124#comment-2340 I have not had a chance to release it yet. Alas, I am no longer at the company I developed the framework for, but I would like to release it at some point once I clean it up. Sorry for the delays, but I have a lot going on right now. I have not had a chance to release it yet. Alas, I am no longer at the company I developed the framework for, but I would like to release it at some point once I clean it up. Sorry for the delays, but I have a lot going on right now.

]]> Comment on Using Ruby to Migrate Databases by Charles http://www.linuxbloke.com/2008/08/09/using-ruby-to-migrate-databases/#comment-2339 Charles Wed, 06 Jan 2010 17:55:45 +0000 http://www.linuxbloke.com/?p=124#comment-2339 Did you end up releasing your framework for this? Did you end up releasing your framework for this?

]]> Comment on The Difference Between Multithreaded and Multicore Programming by Andy Ellicott http://www.linuxbloke.com/2009/06/29/the-difference-between-multithreaded-and-multicore-programming/#comment-2338 Andy Ellicott Mon, 17 Aug 2009 05:39:47 +0000 http://www.linuxbloke.com/?p=245#comment-2338 You won't get any arguments from me re: the advantages of columnar vs. row-oriented storage and processing for analytic (data warehousing workloads). But I don't agree that the benefits of multi-core databases are limited to handling large volumes of data in in query-intensive apps. Nor is multi-threading necessarily the best answer for heavy/extreme OLTP workloads. Multi-core DBMS appear to enable higher transaction throughput in OLTP workloads (and better scalability). This is due in part to the elimination of multi-threading logic in the DBMS (latching, et al), which can compose ~14% of the overhead associated with the processing of a transaction. Check out this paper from the 2008 SIGMOD conference: <a href="http://cs-www.cs.yale.edu/homes/dna/papers/oltpperf-sigmod08.pdf" rel="nofollow">http://cs-www.cs.yale.edu/homes/dna/papers/oltpperf-sigmod08.pdf</a> It does a great job explaining the DBMS overhead associated with the execution of a transaction and also asserts that 90% of it is a by-product of legacy OLTP requirements and no longer necessary. One of the co-authors of the paper, Mike Stonebraker, has co-founded a company developing a multi-core OLTP DBMS called <a href="http://www.voltdb.com" rel="nofollow">VoltDB</a>. You won’t get any arguments from me re: the advantages of columnar vs. row-oriented storage and processing for analytic (data warehousing workloads).

But I don’t agree that the benefits of multi-core databases are limited to handling large volumes of data in in query-intensive apps. Nor is multi-threading necessarily the best answer for heavy/extreme OLTP workloads. Multi-core DBMS appear to enable higher transaction throughput in OLTP workloads (and better scalability). This is due in part to the elimination of multi-threading logic in the DBMS (latching, et al), which can compose ~14% of the overhead associated with the processing of a transaction.

Check out this paper from the 2008 SIGMOD conference: http://cs-www.cs.yale.edu/homes/dna/papers/oltpperf-sigmod08.pdf

It does a great job explaining the DBMS overhead associated with the execution of a transaction and also asserts that 90% of it is a by-product of legacy OLTP requirements and no longer necessary.

One of the co-authors of the paper, Mike Stonebraker, has co-founded a company developing a multi-core OLTP DBMS called VoltDB.

]]> Comment on Using Ruby to Migrate Databases by Phil Schalm http://www.linuxbloke.com/2008/08/09/using-ruby-to-migrate-databases/#comment-2319 Phil Schalm Fri, 03 Jul 2009 05:37:17 +0000 http://www.linuxbloke.com/?p=124#comment-2319 Hi Fred, I posted a comment earlier asking if you had gotten permission to post the code you'd developed or could offer any insight to someone looking to do the same thing, but it appears my comment got deleted. Anyway, I am re-iterating my previous question about the status of the code. Thanks! Hi Fred,

I posted a comment earlier asking if you had gotten permission to post the code you’d developed or could offer any insight to someone looking to do the same thing, but it appears my comment got deleted. Anyway, I am re-iterating my previous question about the status of the code.

Thanks!

]]> Comment on The Difference Between Multithreaded and Multicore Programming by Justin Swanhart http://www.linuxbloke.com/2009/06/29/the-difference-between-multithreaded-and-multicore-programming/#comment-2316 Justin Swanhart Mon, 29 Jun 2009 20:50:24 +0000 http://www.linuxbloke.com/?p=245#comment-2316 Don't look to MySQL AB to resolve multi-core issues with MySQL. For the most part MySQL has always been and will continue to be an OLTP database, for which multithreading is a tried-and-true approach. Where multiple cores really come into play is in handling vast amounts of data. Row-oriented storage engines have lots of issues at scale. What is needed is a column oriented storage engine which can process a single query in more than one thread. But you don't have to wait for the future. The <a href="http://www.kickfire.com" rel="nofollow">The Kickfire Analytics Appliance</a> features a column store and a unique patented SQL chip with which to process queries in parallel. Don’t look to MySQL AB to resolve multi-core issues with MySQL. For the most part MySQL has always been and will continue to be an OLTP database, for which multithreading is a tried-and-true approach. Where multiple cores really come into play is in handling vast amounts of data.

Row-oriented storage engines have lots of issues at scale. What is needed is a column oriented storage engine which can process a single query in more than one thread.

But you don’t have to wait for the future. The The Kickfire Analytics Appliance features a column store and a unique patented SQL chip with which to process queries in parallel.

]]> Comment on Of Character Sets, MySQL, and localization woes… by Shlomi Noach http://www.linuxbloke.com/2009/02/19/of-character-sets-mysql-and-localization-woes/#comment-240 Shlomi Noach Fri, 20 Feb 2009 12:07:31 +0000 http://www.linuxbloke.com/?p=214#comment-240 Hi, Good post. Allow my to link to <a href="http://code.openark.org/blog/mysql/mysqls-character-sets-and-collations-demystified" rel="nofollow">MySQL’s character sets and collations demystified</a>, a post I wrote which explains how character sets and collations work in MySQL, as well as some best practices to use. "I find it quite puzzling that in this day and age of globalization that many of the tools don’t default to UTF8." I couldn't agree more. For some years now I'm thinking "it will all be over with withing a few years", but so many websites are still working with locale specific charsets, I now feel les optimistic. Regards Hi,

Good post.
Allow my to link to MySQL’s character sets and collations demystified, a post I wrote which explains how character sets and collations work in MySQL, as well as some best practices to use.

“I find it quite puzzling that in this day and age of globalization that many of the tools don’t default to UTF8.”
I couldn’t agree more. For some years now I’m thinking “it will all be over with withing a few years”, but so many websites are still working with locale specific charsets, I now feel les optimistic.

Regards

]]> Comment on Of Character Sets, MySQL, and localization woes… by Unicode coming to PHP 6 « MySQLTalk.com http://www.linuxbloke.com/2009/02/19/of-character-sets-mysql-and-localization-woes/#comment-234 Unicode coming to PHP 6 « MySQLTalk.com Thu, 19 Feb 2009 20:07:37 +0000 http://www.linuxbloke.com/?p=214#comment-234 [...] tough part is even if you get the character sets running correctly, the tools you use to view the output may still be [...] [...] tough part is even if you get the character sets running correctly, the tools you use to view the output may still be [...]

]]>