|author||jtang <jtang@web>||2011-08-01 11:16:19 (GMT)|
|committer||Jimmy Tang <email@example.com>||2011-08-01 11:16:19 (GMT)|
|commit||2ca4a52411f6a3737d23182cd84c505e8e8ca57e (patch) (side-by-side diff)|
1 files changed, 4 insertions, 0 deletions
diff --git a/blog/posts/IO_can_be_a_killer_even_on_small_pieces_of_code.mdwn b/blog/posts/IO_can_be_a_killer_even_on_small_pieces_of_code.mdwn
index 3eeb3fc..866a1ee 100644
@@ -1,3 +1,7 @@
[[!tag linux software draft]]
+Having spent a week or two at fixing up a code for "Genetic Classification of Populations Using Supervised Learning" was interesting as it was, but I was baffled at why there were constant fopen's and fclose's for loading up an input file that never got altered.
+Removing the fopen/fclose calls to point to a piece of memory automagically made the the code run about 20% faster. The code isn't as slow as I thought it was going to be, it runs at quite an acceptable rate now.
[[!template id=related tagged="tagged(software) or tagged(linux)"]]