Re: Merging files, 1 line for every 10

in reply to Merging files, 1 line for every 10

What a very strange concept. I can see no real practical use for such a thing.

Homework?

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

Comment on Re: Merging files, 1 line for every 10
Re^2: Merging files, 1 line for every 10 by Luxin (Initiate) on Sep 07, 2011 at 13:27 UTC
LOL - No, not homework. I am performance testing a system that uses multiple data repositories. In Production, about 10% of requests get serviced by system A, and 90% get serviced by system B. To properly mimic production I need to load test the system with similar requests, hence the 10/90 split.	[reply]
Re^3: Merging files, 1 line for every 10 by CountZero (Chancellor) on Sep 07, 2011 at 21:21 UTC
OK. But doing a "1 line from file A followed by 9 lines from file B", you are actually handling a degenerate case where all requests are artificially spaced in an even way. Wouldn't it be more "real" to randomly determine from which file to read the next request: `if (int(rand(10) = 0)) { # read from file A } else { # read from file B }` [download] 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	[reply] [d/l]


laziness, impatience, and hubris
	PerlMonks

Re: Merging files, 1 line for every 10

How many continents have you visited?