Difference between revisions of "PartKeepr on Raspberry Pi"
m (→Raspberry Pi 3 with Raspbian Stretch) |
|||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | PartKeepr can run on a Raspberry Pi. | + | PartKeepr can run on a Raspberry Pi. |
| − | == Raspberry Pi == | + | == Recommended Raspberry Pi configuration == |
| + | === Raspberry Pi 3 with Raspbian Stretch === | ||
| − | == Raspberry Pi 2 == | + | PartKeepr 1.4.0 was tested on Raspberry Pi 3 running Raspbian Stretch, Apache, and PHP 7.0. |
| + | |||
| + | Page load from login takes about 2.8 seconds, with subsequent page loads taking ~1 second, and deemed quite usable. | ||
| + | |||
| + | PHP maximum_execution and PHP-APCu was installed (as mentioned in the Raspberry Pi 2 notes below). | ||
| + | |||
| + | See the [[PartKeepr 1.4.0 installation on a Raspberry Pi]] guide for further details. | ||
| + | |||
| + | == Other Raspberry Pi configurations (Archive) == | ||
| + | |||
| + | === Raspberry Pi 4 with Raspbian Buster === | ||
| + | |||
| + | As the Raspberry Pi 4 does not support the older Raspbian Stretch (currently only runs the newer Raspbian Buster), the instructions above are not compatible with a Raspberry Pi 4 installation. | ||
| + | |||
| + | Testing was done to install PartKeepr 1.4.0 on Raspbian Buster. However, whilst installation was possible, there were a number of problems and malfunctions. This is believed to be a compatibility issue with with the newer PHP APCu version that comes with Buster and the Symfony2 implementation. | ||
| + | |||
| + | === Raspberry Pi === | ||
| + | |||
| + | '''Note: The following information is outdated'''; please read [[APC_Metadata_Caching]] for running PartKeepr on your 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 === | ||
| + | |||
| + | '''Note: The following information is outdated'''; please read [[APC_Metadata_Caching]] for running PartKeepr on your Raspberry Pi. | ||
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. | 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. | ||
Latest revision as of 00:56, 9 November 2020
PartKeepr can run on a Raspberry Pi.
Contents
Recommended Raspberry Pi configuration
Raspberry Pi 3 with Raspbian Stretch
PartKeepr 1.4.0 was tested on Raspberry Pi 3 running Raspbian Stretch, Apache, and PHP 7.0.
Page load from login takes about 2.8 seconds, with subsequent page loads taking ~1 second, and deemed quite usable.
PHP maximum_execution and PHP-APCu was installed (as mentioned in the Raspberry Pi 2 notes below).
See the PartKeepr 1.4.0 installation on a Raspberry Pi guide for further details.
Other Raspberry Pi configurations (Archive)
Raspberry Pi 4 with Raspbian Buster
As the Raspberry Pi 4 does not support the older Raspbian Stretch (currently only runs the newer Raspbian Buster), the instructions above are not compatible with a Raspberry Pi 4 installation.
Testing was done to install PartKeepr 1.4.0 on Raspbian Buster. However, whilst installation was possible, there were a number of problems and malfunctions. This is believed to be a compatibility issue with with the newer PHP APCu version that comes with Buster and the Symfony2 implementation.
Raspberry Pi
Note: The following information is outdated; please read APC_Metadata_Caching for running PartKeepr on your 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
Note: The following information is outdated; please read APC_Metadata_Caching for running PartKeepr on your Raspberry Pi.
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.
