path: root/benchmark
diff options
authornormal <normal@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>2017-10-01 21:19:24 (GMT)
committernormal <normal@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>2017-10-01 21:19:24 (GMT)
commite552afc30ee8f225ed7b6f798cb783ef08d7a737 (patch)
tree2f622b4b4caeefe6aaf3db1683e1b42b305c7baa /benchmark
parentf01846cdc84975748717aa049442896ff3a04a8f (diff)
File#rename releases GVL
rename(2) requires two pathname resolution operations which can take considerable time on slow filesystems, release the GVL so operations on other threads may proceed. On fast, local filesystems, this change results in some slowdown as shown by the new benchmark. I consider the performance trade off acceptable as cases are avoided. benchmark results: minimum results in each 3 measurements. Execution time (sec) name trunk built file_rename 2.648 2.804 Speedup ratio: compare with the result of `trunk' (greater is better) name built file_rename 0.944 * file.c (no_gvl_rename): new function (rb_file_s_rename): release GVL for renames * benchmark/bm_file_rename.rb: new benchmark git-svn-id: svn+ssh:// b2dd03c8-39d4-4d8f-98ff-823fe69b080e
Diffstat (limited to 'benchmark')
1 files changed, 11 insertions, 0 deletions
diff --git a/benchmark/bm_file_rename.rb b/benchmark/bm_file_rename.rb
new file mode 100644
index 0000000..3bf6a5e
--- /dev/null
+++ b/benchmark/bm_file_rename.rb
@@ -0,0 +1,11 @@
+# rename file
+require 'tempfile'
+max = 100_000
+tmp = ['rename-a'),'rename-b') ]
+a, b = { |x| x.path }
+max.times do
+ File.rename(a, b)
+ File.rename(b, a)
+tmp.each { |t| t.close! }