|
|
|
|||||||||||||||||
| JOURNAL HOME | HELP | CONTACT PUBLISHER | SUBSCRIBE | ARCHIVE | SEARCH | TABLE OF CONTENTS |
Geotrace Technologies, Houston, Texas, U.S.
Corresponding author: jweigant@geotrace.com
| The first 20% of the full text of this article appears below. |
"We have 1024 CPUs in our cluster."
"This imaging job will be run on our 2000 CPU Linux cluster."
"We have over 3000 CPUs dedicated to seismic processing."
How many times have oil company representatives heard lines like these? How many times have those of us in the seismic processing industry delivered lines like these? Most importantly, does it really matter how many CPUs you have?
With the advent of low-cost Linux clusters, seismic processing options such as large-scale prestack depth migration and wave-equation migration became feasible on a commercial level. In turn, in the never-ending cycle of one-upsmanship that goes on among contractors, the number of CPUs in a company's Linux cluster became a new metric. But is this really the right measure of "processing power" or throughput capabilities?
For the sake of this particular argument, let's ignore some of the more unscrupulous ways that CPU count has been abused in the
This article has been cited by other articles:
![]() |
R. R. Jones, K. J. W. Mccaffrey, J. Imber, R. Wightman, S. A. F. Smith, R. E. Holdsworth, P. Clegg, N. De Paola, D. Healy, and R. W. Wilson Calibration and validation of reservoir models: the importance of high resolution, quantitative outcrop analogues Geological Society, London, Special Publications, January 1, 2008; 309(1): 87 - 98. [Abstract] [Full Text] [PDF] |
||||
| JOURNAL HOME | HELP | CONTACT PUBLISHER | SUBSCRIBE | ARCHIVE | SEARCH | TABLE OF CONTENTS |