Take the 2-minute tour ×
Computer Science Stack Exchange is a question and answer site for students, researchers and practitioners of computer science. It's 100% free, no registration required.

I wonder where those terms came from.

Is it computer science related?

Or are they related to civil engineering, or swimming sports?

Is it some analogy with filling water in a pool, or something like that?

share|improve this question
    
I you voted down could please tell why? –  rraallvv Jan 30 '13 at 4:22
    
Both pool and leak are daily use words. I have water leak from roof. The leak can potentially make a pool, in a slow manner, of course. –  scaaahu Jan 30 '13 at 6:18
add comment

1 Answer 1

Yes, Computer Science.

Back in the days of the NASA/Apollo program (and possibly before), mainframe computers had wads of memory (like as much as 256 Mwords). To support multi-tasking, a program/task running on that mainframe had to specify how much memory was required to do its job, and the system would allocate that much - if possible - out of the "memory pool". This "pool" nomenclature comes at a time when we had motor pools, secretarial pools, labor pools... nonspecific resources of a certain class; indeed, this working memory on a mainframe was not dedicated to a specific use (there are regions of mainframe memory that are not available to "normal" programs/tasks).

As the tasks run, they are supposed to only use what they ask for, and they are required to signal the system when the memory is no longer needed. Depending on efficiency concerns, they may ask for the memory a little at a time (it's nice for other tasks that you don't grab either everything available, or more than you need). Poorly developed programs have a nasty side-effect of not returning what was allocated to them. From the system's perspective, the available memory pool is getting smaller and smaller, hence the memory "leaks out". It doesn't go anywhere, but the net effect is that a program that needs a certain amount of memory to either load or run will have to wait until a better behaved program/task returns a sufficient part of the allocation - or the memory system is restarted.

share|improve this answer
1  
Citation/Reference, please. –  scaaahu Jan 30 '13 at 10:23
    
I used to be a mainframe programmer in the 70s. I saw your comment to the downvote and just LMAO. en.wikipedia.org/wiki/… (memory pool, see section on "MVT") en.wikipedia.org/wiki/Memory_leak#cite_note-1 (memory leak) - hope that helps. –  Jimzie Jan 30 '13 at 16:00
    
I did not downvote your answer. To answer your response, we need to know who first used the terms memory pool and memory leak. Not who have used them. I myself used to be a computer operator for 360/370 and UNIVAC. I do know those stuff. That's not the point. The OP's question was, where they came from? civil eng./swimming pool? I think not. –  scaaahu Jan 31 '13 at 5:55
    
I was under the impression that you downvoted the question, not my answer. However, "The leak can potentially make a pool" is decidedly inconsistent usage within the topic of computer memory management - in any era to date. –  Jimzie Jan 31 '13 at 6:02
1  
Back in my day we used Mercury for our memory pools and you had to avoid leaks because they made programmers crazy. This is, coincidentally, also the source of the term 'mad skills'. –  adrianN Jan 31 '13 at 9:58
show 1 more comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.