0

i'm trying out a PHP Encoder called source guardian..

https://www.sourceguardian.com/

as with other encoders it promises faster page loads..

but i noticed that my encoded php files are marginally bigger than my original files.. how can that be faster?

Just wanted to check with any SG users here on stack if they're experiencing any bloated files and if it affects performance?

Satish Sharma
  • 9,547
  • 6
  • 29
  • 51
BrownChiLD
  • 3,545
  • 9
  • 43
  • 61

1 Answers1

0

Just bigger filesize doesn't mean slower page loads. They could be doing it like HHVM and compiling it [J]ust [I]n [T]ime in binary. That does make the page loads faster. Incredible faster. Tested it on a production environment. At least 3 times faster than with PHP5-FPM.

Charlotte Dunois
  • 4,638
  • 2
  • 20
  • 39
  • ahh.. did you mean you tested Source Guardian on a prod environment? – BrownChiLD Aug 02 '14 at 11:10
  • No, I was talking about HHVM, because they're using a JIT compiler and compiling the php code in binary to produce massive faster page loads (2-25x) and less memory usage. But Source Guardian could be doing it the same. I don't really know Source Guardian and their source code, so I don't really know how they're really doing it. – Charlotte Dunois Aug 02 '14 at 11:12
  • ahh thanks for the clarification... but for me, SG encoded files doesnt look binary.. here's what part of it looks like : sg_load('ABB6C1703A2482A1AAQAAAAWAAAABGgAAACABAAAAAAAAAD/86QMI2AyxCHKYhUjAK8UzJN3EYcO/mtMvDZ3u1uhbCQO8GoZWLQOyQSn4M8Y6e2uK/fd84A/ZOtnP1/Pln9DH5zYQYAYJxSREghGvRchV8bZrjSvQTTD19fgRtCsSDrW05YpFq6xWJc2AAA – BrownChiLD Aug 02 '14 at 12:14
  • Yes, because it's encoded. The compiled file could be binary. – Charlotte Dunois Aug 02 '14 at 12:23