Skip to content

Instantly share code, notes, and snippets.

View frankmayer's full-sized avatar
🌱
Focusing

Frank Mayer frankmayer

🌱
Focusing
22 followers · 14 following
View GitHub Profile
@dongilbert
dongilbert / config.php
Created August 2, 2012 14:18
Override Core Joomla! Classes
<?php
/**
* @package Joomla.Plugin
* @subpackage System.Overrides
*
* @copyright Copyright (C) 2012 Don Gilbert. All rights reserved.
* @license GNU General Public License version 2 or later; see LICENSE
*/
define('OVERRIDES', dirname(__FILE__).'/overrides');
@Kindari
Kindari / example.php
Created September 19, 2012 23:27
Locale aware Api routing in Laravel 3
<?php // bundles/api_v1/controllers/example.php
class Api_V1_Example_Controller extends Controller
{
public $restful = True;
public function get_hello($name='World')
{
return "Hello, {$name}!";
}
@bsalim
bsalim / php speed up tips.html
Created January 3, 2013 09:09
63 Tips for speeding up PHP
<html>
<body>
<p>Here are Webber’s points:</p>
<ul>
<li>If a method can be static, declare it static. Speed improvement is by a factor of 4.</li>
<li>echo is faster than print.(<em>* compare with list from phplens by John Lim</em>)</li>
<li>Use echo’s multiple parameters instead of string concatenation.</li>
<li>Set the maxvalue for your for-loops before and not in the loop.</li>
<li>Unset your variables to free memory, especially large arrays.</li>
<li>Avoid magic like __get, __set, __autoload</li>
@patrickallaert
patrickallaert / Results.txt
Last active December 14, 2015 02:39
Comparing CPU time and memory usage between classes and arrays.
PHP 5.4:
========
$ php54 bench1.php
0.36937880516052
292432712
$ php54 bench2.php
0.47057294845581
193929016
@nikic
nikic / objects_arrays.md
Last active September 24, 2024 14:51
Post explaining why objects often use less memory than arrays (in PHP)

Why objects (usually) use less memory than arrays in PHP

This is just a small post in response to [this tweet][tweet] by Julien Pauli (who by the way is the release manager for PHP 5.5). In the tweet he claims that objects use more memory than arrays in PHP. Even though it can be like that, it's not true in most cases. (Note: This only applies to PHP 5.4 or newer.)

The reason why it's easy to assume that objects are larger than arrays is because objects can be seen as an array of properties and a bit of additional information (like the class it belongs to). And as array + additional info > array it obviously follows that objects are larger. The thing is that in most cases PHP can optimize the array part of it away. So how does that work?

The key here is that objects usually have a predefined set of keys, whereas arrays don't:




  


  




    


          
    

      

        
        

          

              @havvg
          

          

            
                havvg
                / AcmeController.php
            
            

              Last active
              November 2, 2019 07:29
            

              
                Example for http://www.whitewashing.de/2013/04/12/traits_are_static_access.html
              
          

        

      

        

  

    
    


        



  


  

        

          
          <?php
        

        

          
          

        

        

          
          class AcmeController implements ContainerAwareInterface
        

        

          
          {
        

        

          
              use ContainerAwareTrait;
        

        

          
              use RedirectTrait;
        

        

          
          

        

        

          
              public function indexAction()
        

        

          
              {
        

        

          
                  return $this->redirect('some_route', [
        

  





    


  




    


          
    

      

        
        

          

              @samselikoff
          

          

            
                samselikoff
                / future-proof.md
            
            

              Last active
              August 15, 2024 15:17
            

              
                Future-proofing your Ember 1.x code
              
          

        

      

        

  

      

    
This post is also on my blog, since Gist doesn't support @ notifications.




Components are taking center stage in Ember 2.0. Here are some things you can do today to make the transition as smooth as possible:


    

  • Use Ember CLI
    • 

  • In general, replace views + controllers with components
    • 

  • Only use controllers at the top-level for receiving data from the route, and use Ember.Controller instead of Ember.ArrayController or Ember.ObjectController
    • 

  • Fetch data in your route, and set it as normal properties on your top-level controller. Export an Ember.Controller, otherwise a proxy will be generated. You can use Ember.RSVP.hash to simulate setting normal props on your controller.
    • 




  


  




    


          
    

      

        
        

          

              @nkt
          

          

            
                nkt
                / Results.md
            
            

              Last active
              September 27, 2023 08:24
            

              
                ReactPHP vs Node.js
              
          

        

      

        

  

      

    
wrk -t4 -c400 -d10s http://127.0.0.1:1337/


PHP


Running 10s test @ http://127.0.0.1:1337/
  4 threads and 400 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
 Latency 7.02ms 6.94ms 82.86ms 85.27%