Thing is when I ran it twice on my own hardware (CIFS share, Windows 8.1 client), I got 15 & 14 files/sec, which matched his own Windows performance on his own hardware, Windows 8.1 client, Debian server.
And running the same code on his Mac client yields MUCH faster results
Though I just realized that he is writing out a file list to a local file at the same time as he's reading from the share, maybe his program is performance constrained on local disk access since he's doing that.
Curious if Java will disable output if I pass it nul as an output file
As mentioned, you can create and manipulate files and folders with reserved names on the command line by using a device or filename namespace such as \\.\C:\NUL, but look at what happens when you try to access such a file or folder through Windows Explorer:
Any access to an object with a rese...
@BenRichards The Win32 API doesn't allow it. The kernel doesn't care. If you were going via the POSIX layer (e.g. SUA) or otherwise bypassing Win32, then it's allowed.
@BenRichards I'm writing a test program of my own gimme a sec
Yup.
Measure-Command { .\do_something.ps1 }
Note that one minor downside of Measure-Command is that you see no stdout output. If you want to see the output, then you can use the .NET Stopwatch object e.g.:
$sw = [Diagnostics.Stopwatch]::StartNew()
.\do_something.ps1
$sw.Stop()
$sw.Elapsed
1. I don't have a Java environment on this laptop, 2. I don't intend to install a Java environment if I don't need to, and 3. I wouldn't use Java even if it was an option.
I am going to write a powershell script that gets various statistics on the dir it is in.
If I do
get-childitem
I get this
d---- 06/23/2014 2:49 PM asdf;
-a--- 06/23/2014 2:49 PM 23 New Text Document - Copy (2).txt
-a--- 06/23/2014 2:49 PM ...
$source = @"
using System.Diagnostics;
using System.IO;
using System;
public static class P {
public static void test() {
Stopwatch sw = new Stopwatch();
string root = "C:\\Intel\\";
string output = Path.GetTempFileName() + ".txt";
uint dirs = 0;
uint files = 0;
using (StreamWriter writer = new StreamWriter(output))
{
sw.Start();
foreach (FileSystemInfo fsi in new DirectoryInfo(root).EnumerateFileSystemInfos("*", SearchOption.AllDirectories))
{
if ((fsi.Attributes & FileAttributes.Directory) == FileAttributes.Directory)
I asked him to throw his code up on pastebin or something so we can have a look. My best guess is it's I/O constrained and he's just measuring how aggressively the OS flushes an output file buffer to disk.
I dunno, maybe you need the semicolon at the end? I had the write-host call after as @Bob had in his version but it didn't make it to the actual console output because Measure-Command eats any output from its command block.
depending on how hard the flush is (how hard does it try to force the file to be written to disk) and the OS implementation, that could easily introduce milliseconds per op delay on a HDD
fairly trivial change to make it generic - remove the Ookii VistaFolderBrowserDialog
was just easier to use it
in fact, I'd expect the C# impl to be slightly slower because it theoretically performs filtering (wildcard *)... but possibly faster if it hands off to a native Win32 impl?
It could be a simple python or perl script, even. I've made scripts that recursively walk through a directory before. Just keep low overhead or even only count time when doing the directory list itself.
Benchmark coding is its own skillset. Coding for efficiency isn't something that's necessary for most coding projects anymore due to the hardware being so powerful these days.
But yeah, when I code, minimizing round trips is one of those things that I do by habit because doing more round trips than is necessary just feels wrong to me.
And searching the user list doesn't show anything I recognize. Does it only update periodically?
He didn't post a question or anything on here. I was chatting with him via twitter and offline. I brought the question here since I didn't know enough.
As mentioned, you can create and manipulate files and folders with reserved names on the command line by using a device or filename namespace such as \\.\C:\NUL, but look at what happens when you try to access such a file or folder through Windows Explorer:
Any access to an object with a rese...
Yup.
Measure-Command { .\do_something.ps1 }
Note that one minor downside of Measure-Command is that you see no stdout output. If you want to see the output, then you can use the .NET Stopwatch object e.g.:
$sw = [Diagnostics.Stopwatch]::StartNew()
.\do_something.ps1
$sw.Stop()
$sw.Elapsed
I am going to write a powershell script that gets various statistics on the dir it is in.
If I do
get-childitem
I get this
d---- 06/23/2014 2:49 PM asdf;
-a--- 06/23/2014 2:49 PM 23 New Text Document - Copy (2).txt
-a--- 06/23/2014 2:49 PM ...
