Re^14: randomising file order returned by File::Find

in reply to Re^13: randomising file order returned by File::Find
in thread randomising file order returned by File::Find

"I'm simply countering your suggestion that Hadoop is a one-size-fits-all solution."

Oh i never said that. But since you did not answer "yes" nor "no" ... we can conclude that no, you have never used Hadoop in production.

By the way ... did the OP ever specify exactly what kind of processing was needed? No. Not all image processing has to be CPU bound, after all. ;)

jeffa

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)

Comment on Re^14: randomising file order returned by File::Find Select or Download Code
Re^15: randomising file order returned by File::Find by BrowserUk (Pope) on Mar 02, 2011 at 03:02 UTC
But since you did not answer "yes" nor "no" ... we can conclude that no, you have never used Hadoop in production. And since you've completely failed to respond to any of the reasons why Hadoop is inappropriate for the task at hand we can conclude that you don't have a clue about image processing. Simply a case of the hammer wielder seeing everything as a nail. Last year it was "use a database"; this year "ooh, ooh, ooh, Hadoop" regardless of the problem, and next year it'll no doubt be Node:js. Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice.	[reply]
Re^16: randomising file order returned by File::Find by jeffa (Chancellor) on Mar 02, 2011 at 03:06 UTC
"Last year it was "use a database"; this year "ooh, ooh, ooh, Hadoop"" Just pointing out that you are rejecting technology unfairly. Without even having tried it. Which you have not, even though you tailor your language to imply that you have. jeffa L-LL-L--L-LL-L--L-LL-L-- -R--R-RR-R--R-RR-R--R-RR B--B--B--B--B--B--B--B-- H---H---H---H---H---H--- (the triplet paradiddle with high-hat)	[reply] [d/l] [select]
Re^17: randomising file order returned by File::Find by BrowserUk (Pope) on Mar 02, 2011 at 03:53 UTC
I've not rejected Hadoop. I even suggested it here a couple of weeks ago. I'm simply not recommending it for this as it is inappropriate. To summarise: You cannot force fit variable size and (typically huge) 3D image files into fix-sized aggregated packets; nor can you process images line-by-line from STDIN as is required by Hadoop streaming. I'm not rejecting the tool; I'm reject the suggestion for mis-application of that tool. The OP reads and makes up his own mind on the matter. Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice.	[reply]
Re^18: randomising file order returned by File::Find by jeffa (Chancellor) on Mar 02, 2011 at 04:20 UTC
Re^19: randomising file order returned by File::Find by BrowserUk (Pope) on Mar 02, 2011 at 04:29 UTC
Some notes below your chosen depth have not been shown here


Keep It Simple, Stupid
	PerlMonks

Re^14: randomising file order returned by File::Find

The best material for plates (tableware) is: