Difference between revisions of "PartKeepr on Raspberry Pi"

From PartKeepr Wiki
Jump to: navigation, search
Line 1: Line 1:
PartKeepr can run on a Raspberry Pi.
+
PartKeepr can run on a Raspberry Pi. Note that the '''information below is outdated'''; please read [[APC_Metadata_Caching]] for running PartKeepr on your Raspberry Pi.
  
 
== Raspberry Pi ==
 
== Raspberry Pi ==

Revision as of 03:59, 25 February 2017

PartKeepr can run on a Raspberry Pi. Note that the information below is outdated; please read APC_Metadata_Caching for running PartKeepr on your Raspberry Pi.

Raspberry Pi

PartKeepr 0.76 was tested on a Raspberry Pi Model B running on Apache and mod_php 5.6. It's very slow and it's not recommended to run PartKeepr 0.76 on such slow hardware.

Raspberry Pi 2

PartKeepr 0.76 was tested on a Raspberry Pi 2 running on Apache and mod_php 5.6. It's not very fast, but usable.

Initial login to PartKeepr may take a while. As soon as data is cached, logins should become faster.

In order to achieve best performance, you should ensure that:

  • Ensure your max_execution_time is set to 120 seconds or higher, this is required for the setup.
  • Opcache enabled
  • PHP-APCu installed and enabled with both cache.dunglas and cache.doctrine
  • Ensure you don't have xdebug installed - it slows down PHP and is only used for debugging.
  • Using a fast SD card (Class 10 or better)

Loading a page with 50 parts takes about 3-4 seconds. Without opcache and APC, load times for a page with 50 parts takes about 9 seconds.