Downloads of v 1.0.0-alpha:


Last Update:

09 Nov 2021

Package Maintainer(s):

Software Author(s):

  • Tino Reichardt


Windows Benchmark cli RunningTime KernelTime time memory io


This is a prerelease version of Wtime.

  • 1
  • 2
  • 3

1.0.0-alpha | Updated: 09 Nov 2021



Downloads of v 1.0.0-alpha:



Software Author(s):

  • Tino Reichardt

  • 1
  • 2
  • 3
Wtime 1.0.0-alpha

This is a prerelease version of Wtime.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Passed


Scan Testing Resulted in Flagged as a Note:

At least one file within this package has greater than 0 detections, but less than 5

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Wtime, run the following command from the command line or from PowerShell:


To upgrade Wtime, run the following command from the command line or from PowerShell:


To uninstall Wtime, run the following command from the command line or from PowerShell:


Deployment Method:

📝 NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to

2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Copy Your Script

choco upgrade wtime -y --source="'INTERNAL REPO URL'" --prerelease [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade wtime -y --source="'INTERNAL REPO URL'" --prerelease

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Install wtime
    name: wtime
    version: '1.0.0-alpha'
    state: present
    allow_prerelease: yes

See docs at

chocolatey_package 'wtime' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '1.0.0-alpha'
  options  '--prerelease'

See docs at

cChocoPackageInstaller wtime
    Name        = "wtime"
    Version     = "1.0.0-alpha"
    Source      = "INTERNAL REPO URL"
    chocoParams = "--prerelease"

Requires cChoco DSC Resource. See docs at

package { 'wtime':
  ensure          => '1.0.0-alpha',
  install_options => ['--prerelease'],
  provider        => 'chocolatey',
  source          => 'INTERNAL REPO URL',

Requires Puppet Chocolatey Provider module. See docs at

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package is exempt from moderation. While it is likely safe for you, there is more risk involved.

The program will start COMMAND with the given OPTIONS and print out some statistic of it to stderr.

Sample output:

command: 7z a silesia.7z -mmt=off -mx15 silesia

TIMES in milliseconds
RunningTime................. 32104
UserTime.................... 31793
KernelTime.................. 249

PageFaultCount.............. 112
PeakWorkingSetSize.......... 34856
WorkingSetSize.............. 20
QuotaPeakPagedPoolUsage..... 85
QuotaPagedPoolUsage......... 0
QuotaPeakNonPagedPoolUsage.. 6
QuotaNonPagedPoolUsage...... 0
PagefileUsage............... 0
PeakPagefileUsage........... 36296

IO count
ReadOperationCount.......... 81
WriteOperationCount......... 34
OtherOperationCount......... 115
ReadTransferCount........... 211939037
WriteTransferCount.......... 58043652
OtherTransferCount.......... 3414

$ErrorActionPreference = "Stop";

$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  unzipLocation = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
  url           = ""
  url64bit      = ""
  file         = "$(Join-Path (Split-Path -parent $MyInvocation.MyCommand.Definition) "wtime.exe")"
  softwareName  = "wtime*"
  checksum      = "aeca0ac651097837db8ff156609919e178844cd03da6734f330e61bf12b7fc24"
  checksumType  = "sha256"
  checksum64    = "24474e03d5cbc6281987c1cb5c4c98f6149fb4781d8b1158ee37dc736c6ee333"
  checksumType64= "sha256"

Get-ChocolateyWebFile @packageArgs

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status
Wtime 1.0.0-alpha 56 Tuesday, November 9, 2021 Exempted

This package has no dependencies.

Discussion for the Wtime Package

Ground Rules:

  • This discussion is only about Wtime and the Wtime package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Wtime, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus