Wie viel Zeit kosten Funktionsaufrufe in PHP?

100%

Wie viel Zeit kosten Funktionsaufrufe in PHP?

✓ Published0🌍 Public

Last edited Feb 22, 2016

Created on Feb 22, 2016

This example measures the overhead of PHP function calls by generating two scripts: one with 10,000 nested function calls and one with equivalent code using only variables. The code uses PHP’s `microtime` API to time each variant and compares the results. The visualization renders the generated source files and shows the cost per call in seconds, highlighting the performance difference.

AI-generated description

Similar vizzes

Loading thumbnail…

Scripte um zu untersuchen ob die Übertragungsrate nach einem Ping systematisch höher ist

The visualization examines whether network transfer rates are systematically higher after a ping, based on a shell-based client-server experiment. The server repeatedly serves random 1M data blocks via `netcat`, while the client logs timing for transfers before and after each ping using the `time` command. The plot likely reveals any consistent throughput differences, with data sourced from logfile output generated by the Bash scripts. The code relies on standard Unix shell utilities (`netcat`, `dd`, `ping`, `sleep`) and randomized wait intervals between trials.

HHoffmannP

44% match

Loading thumbnail…

Algorithm 1

This example demonstrates the computational complexity of nested loops versus single loops, using JavaScript’s console.log to output results of multiplication operations. The code defines constants and variables to illustrate constant-time operations (O(1)), then shows a single for loop executing in linear time (O(n)), followed by a double for loop with a nested inner loop that runs in quadratic time (O(n^2)). It also includes a second nested loop with an additional constant-time operation, representing c1 * O(n^2). The example uses basic JavaScript syntax with no external libraries, relying on the browser’s console for output.

NNita

43% match

Loading thumbnail…

AB Benchmark Node.js (via Restify) - 10,000 requests (10 concurrent)

This example displays the results of an ApacheBench load test against a Node.js Restify server, showing 10,000 requests completed with 10 concurrent connections. The visualization plots the percentage of requests served within specific time thresholds, from the 50th percentile at 3 milliseconds up to the longest request at 18 milliseconds. The chart uses D3.js to render the distribution of response times, with data parsed from the ApacheBench text output. The visualization highlights the server’s consistent performance, as most requests complete within 4 milliseconds, and reveals the small variance in request handling times.

HHugoberry

42% match

Loading thumbnail…

EventsSpeedTests

This example demonstrates how a single property added to one function—but not all functions—can trigger V8’s “failed to optimize dispatch” warning in a hot loop. It shows the impact of monomorphic versus polymorphic call-sites for `Function.prototype.apply` when dispatching to multiple callbacks. The code runs 2 million iterations of a `dispatch` function that invokes two callbacks, comparing an unoptimized case, a bound-function variant, and a fixed version using `.bind(0)` to enforce a monomorphic apply site. The included HTML interface and Node command-line tests let users measure execution time differences across the three approaches.

HHypercubed

42% match

Loading thumbnail…

recompress jpg files on the fly

This example shows an Apache PHP script that transparently recompresses JPEG images on the fly whenever a browser requests a `.jpg` file. It first displays the original image in response to the request, then uses the external `jpeg-recompress` executable to create a smaller cached version, which subsequent requests serve instead. The script relies on server-side file handling via `filemtime`, `filesize`, and `md5`, and writes a cache log with compression ratios using `error_log`. It conditionally serves cached files only when they are newer than the source.

PPhilippe Rivière

39% match

Loading thumbnail…

PowerArray vs....

This example benchmarks the `forEach` method across multiple JavaScript libraries—native `Array.prototype.forEach`, `fast.js`, `underscore`, and `lodash`—applied to three data types: plain arrays, `Float32Array`, and a custom `PowerArray` class. It shows that native `forEach` on a plain array is the baseline, while `fast.js` and `underscore` achieve similar or better throughput on arrays, with `powerArray.forEach` leading all variants. The code uses `process.hrtime()` for high-resolution timing and computes operations per second from a 10-million-element dataset. Results highlight that typed arrays (`Float32Array`) generally slow down iteration, except with `lodash` and `underscore`, which still lag behind array-based calls.

HHypercubed

39% match

Loading thumbnail…

Flatten an array in Javascript without recursion

This example compares two JavaScript functions for flattening nested arrays, showing that the iterative approach is faster than the recursive one. The code uses the Benchmark.js library to time both methods on a nested array of integers, with the suite reporting each function’s operations per second. The recursive version, `flattenRecursive`, relies on `concat` and `forEach`, while the iterative `flatten` uses a `while` loop with `shift` to mutate the list in place. The output, logged via `console.log`, highlights the fastest method, demonstrating the performance trade-off between recursion and iteration.

HHypercubed

38% match

Loading thumbnail…

number exercises

This example visualizes the outcomes of several JavaScript exercise functions, each testing a specific computation. It shows whether functions like `computeArea`, temperature converters `celsToFahr` and `fahrToCels`, and `isDivisible` produce expected results. The code relies on native JavaScript functions and console logging to report pass or fail statuses, with no external libraries or data sources. The rendering approach is purely textual, using `console.log` output to display success or failure messages for each test case, making the results immediately visible in the console.

CCameron-Grams

38% match