comment on

As was said during the last YAPC::EU in Copenhagen, multiple cores means also a lower clock-speed, so any application that runs in only one core is by definition running slower and is essentially at the mercy of the OS whether its core gets shared with other applications, slowing it down even more.

Not all applications are open to parallel execution. A "read one line, do something with it, write the result to a file, start over again" is basically something sequential that would need a lot of overhead to split it over multiple cores. I think the majority of the scripts we write are of this type.

CountZero

A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James

In reply to Re: Multi-core and the future by CountZero
in thread Multi-core and the future by pileofrogs

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


go ahead... be a heretic
	PerlMonks