Details

Published: 22 March 2021

• php

Sometimes you want to know how long a script took and how much memory it consumed.

Run Time and Memory used can also be useful if tracked overtime, for example in:

• cron/cli scripts
• web requests
• api requests

While tools such as New Relic (paid), DataDog (paid), NetData (opensource), Prometheus (opensource) could be used, sometimes a simpler local solution is all that is needed.

Here is a simple Trait to extend your classes with

<?php

namespace App\Traits;

trait Stats
{
    private $timer_start;
    private $timer_finish;

    public function statsTimerStart()
    {
        $this->timer_start = microtime(true);
    }

    public function statsTimerFinish()
    {
        $this->timer_finish = microtime(true);
    }

    public function statsTimerRuntime()
    {
        if (empty($this->timer_finish)) {
            $this->statsTimerFinish();
        }

Details

Published: 22 February 2021

• php

<?php

// command line only
if (PHP_SAPI != 'cli') {
    exit("CLI only");
}

// 1st arg is calling script, and then should pass in a uri which should map to a route
if (empty($argv) || count($argv) < 2) {
    exit("Missing route for CLI");
}

// remove calling script
array_shift($argv);

// get route + params from 1st argument
$uri = array_shift($argv);

// group routes by /cli/
if (strpos($uri, '/cli/') !== 0) {
    exit("CLI Route must start with /cli/");
}

// get any more arguments
if (!empty($argv)) {
    $additional = '';
    foreach ($argv as $arg) {
        if (strpos($arg, '=') !== false) {
            // cli.php r=1 d=10
            $additional .= '&' . $arg;
        } else {
            // cli.php -r 10
            // normal arguments, store as argv
            $additional .= '&argv[]=' . $arg;
        }
    }
    if (strpos($uri, '?') === false) {
        $uri .= '?';
    }
    $uri .= $additional;
}
// set uri based on cli arguments
$_SERVER['REQUEST_URI'] = $uri;

// normal Slim app
(require __DIR__ . '/your/bootstrap.php');

Details

Published: 15 January 2021

• cypress
• tests

• integration

• fixtures

• plugins

• screenshots

• support

• • commands

• • callbacks

Details

Published: 16 December 2020

• aws
• s3

By putting a cleanup Lifecycle rule in place on your S3 buckets, you may be able to potentially save costs and increase LIST performance.

"Incomplete Multipart Uploads – S3’s multipart upload feature accelerates the uploading of large objects by allowing you to split them up into logical parts that can be uploaded in parallel.  If you initiate a multipart upload but never finish it, the in-progress upload occupies some storage space and will incur storage charges. However, these uploads are not visible when you list the contents of a bucket and (until today’s release) had to be explicitly removed.

Expired Object Delete Markers – S3’s versioning feature allows you to preserve, retrieve, and restore every version of every object stored in a versioned bucket. When you delete a versioned object, a delete marker is created. If all previous versions of the object subsequently expire, an expired object delete marker is left. These markers do not incur storage charges. However, removing unneeded delete markers can improve the performance of S3’s LIST operation."

Source: https://aws.amazon.com/blogs/aws/s3-lifecycle-management-update-support-for-multipart-uploads-and-delete-markers/

To add a cleanup Lifecycle rule:

• Log into the Amazon S3 web console
• Select your S3 bucket

• Select Management
• Select Add lifecycle rule

• Enter a name such as 

'Delete incomplete multipart upload and Delete previous versions'

• Skip Transitions for now

Transitions allow you to move storage to slower locations at a reduced cost
https://docs.aws.amazon.com/AmazonS3/latest/dev/lifecycle-transition-general-considerations.html

• Expiration
  • Delete Previous versions after 365 days

You can choose shorter periods such as 7 days or 30 days if you don’’t have a use case for retrieving prior S3 versions.
You will still have the current version, which is usually all you want, but deleting previous versions can help with costs and S3 LIST performance.

• • Clean up incomplete multipart uploads after 7 days

If you do not have any automated processes that may re-try uploads, you could choose 1 day

• Review

Agree to the 'scary' this applies to all objects in bucket
Note, if you have S3 objects (uploads) which require different policies, you may find it easier to manage by creating a S3 bucket per policy.

You now have some basic cleanup of your S3 bucket(s) configured.