add WordPress templating system specific test

Author: kevindees

object-vs-file-exists/exists.php

@@ -0,0 +1,14 @@
+<?php
+list($script, $option, $n) = $argv;
+$s = microtime(true);
+
+function dispatch() {
+    return file_exists(__FILE__) || file_exists(__FILE__);
+}
+
+$range = range(1,  $n ?? 1);
+foreach ($range as $i) {
+    dispatch();
+}
+
+echo ( microtime(true) - $s) * 1000;

object-vs-file-exists/object.php

@@ -0,0 +1,23 @@
+<?php
+list($script, $option, $n) = $argv;
+$s = microtime(true);
+
+class testObject {
+    public function get()
+    {
+        foreach (['nil', 'null'] as $v) {
+            in_array($v, ['null', 'more', 'nil']);
+        }
+    }
+}
+
+$obj = new testObject;
+
+$range = range(1,  $n ?? 1);
+foreach ($range as $i) {
+    $obj->get();
+    $obj->get();
+    $obj->get();
+}
+
+echo ( microtime(true) - $s) * 1000;

object-vs-file-exists/readme.md

@@ -0,0 +1,16 @@
+A not-so-scientific speed test. In WordPress templates are checked using `file_exists` so I want to compare tha methods speed against a collection of `in_array` tests. The reason for this is because I can skip those `file_exists` checks if I override the WordPress template locating system with an array collection.
+
+Run Commands:
+
+```
+// args: string "starting with a", "num times to run"
+php exists.php a 10000
+php object.php a 10000
+```
+
+### Small Set ~100 calls
+
+- *Object*: `0.425ms`
+- *File*: `0.602ms`
+
+My conclusion is that the replacement can be done without a large performance impact (if not being faster).