Difference between revisions of "Infrastructure Planning"
Jump to navigation
Jump to search
Raphael0202 (talk | contribs) m |
m (Formatting) |
||
Line 7: | Line 7: | ||
* dev: dev server, robotoff, remote backup | * dev: dev server, robotoff, remote backup | ||
− | == Hardware needs | + | == Hardware needs 2020 == |
=== Production === | === Production === | ||
Line 13: | Line 13: | ||
* Frontend + backend for the web site and API | * Frontend + backend for the web site and API | ||
** off1 | ** off1 | ||
+ | |||
* MongoDB | * MongoDB | ||
** off2 | ** off2 | ||
− | * Robotoff | + | |
+ | * '''Robotoff''' | ||
** New server | ** New server | ||
*** Models are memory hungry, at least 32 GB of RAM is needed. Ideally, 64 GB. | *** Models are memory hungry, at least 32 GB of RAM is needed. Ideally, 64 GB. | ||
*** Ideally, 1 GPU server. Otherwise, high-performance CPU are suitable, 8 cores at least (the more, the better). | *** Ideally, 1 GPU server. Otherwise, high-performance CPU are suitable, 8 cores at least (the more, the better). | ||
*** Disk: speed is only important when loading model from disk, which only occurs at startup. Ideally NVMe, classic SSDs are fine. 500 GB of space should be ok. | *** Disk: speed is only important when loading model from disk, which only occurs at startup. Ideally NVMe, classic SSDs are fine. 500 GB of space should be ok. | ||
− | * New producer platform | + | |
+ | * '''New producer platform''' | ||
** New server | ** New server | ||
*** Little web traffic, lots of image data (sometimes in huge PDFs or png) | *** Little web traffic, lots of image data (sometimes in huge PDFs or png) | ||
*** mid-level cpu and ram, at least 2x4 Tb disks | *** mid-level cpu and ram, at least 2x4 Tb disks | ||
− | * New content platform (wiki, blog) ?? | + | |
+ | * '''New content platform''' (wiki, blog...) ?? | ||
** New server for different kind of tools (example: Zammad, MediaWiki, Wordpress, Nextcloud?) | ** New server for different kind of tools (example: Zammad, MediaWiki, Wordpress, Nextcloud?) | ||
*** Little web traffic, not much disk needed (except for videos if needed?) | *** Little web traffic, not much disk needed (except for videos if needed?) | ||
Line 35: | Line 39: | ||
=== Dev === | === Dev === | ||
− | * OFF + producer platform dev | + | * '''OFF + producer platform dev''' |
** New server | ** New server | ||
*** mid level cpu and ram, at least 2x8 Tb disks | *** mid level cpu and ram, at least 2x8 Tb disks |
Revision as of 11:19, 26 August 2020
Current infrastructure
Details on https://en.wiki.openfoodfacts.org/Infrastructure#Current_infrastructure
- off1: frontend + backend for the web site and API
- off2: mongodb + off1 backup
- dev: dev server, robotoff, remote backup
Hardware needs 2020
Production
- Frontend + backend for the web site and API
- off1
- MongoDB
- off2
- Robotoff
- New server
- Models are memory hungry, at least 32 GB of RAM is needed. Ideally, 64 GB.
- Ideally, 1 GPU server. Otherwise, high-performance CPU are suitable, 8 cores at least (the more, the better).
- Disk: speed is only important when loading model from disk, which only occurs at startup. Ideally NVMe, classic SSDs are fine. 500 GB of space should be ok.
- New server
- New producer platform
- New server
- Little web traffic, lots of image data (sometimes in huge PDFs or png)
- mid-level cpu and ram, at least 2x4 Tb disks
- New server
- New content platform (wiki, blog...) ??
- New server for different kind of tools (example: Zammad, MediaWiki, Wordpress, Nextcloud?)
- Little web traffic, not much disk needed (except for videos if needed?)
- mid-level cpu and ram, 2x500 Gb SSD disks probably ok
- New server for different kind of tools (example: Zammad, MediaWiki, Wordpress, Nextcloud?)
Backup
- New backup server or cloud storage
Dev
- OFF + producer platform dev
- New server
- mid level cpu and ram, at least 2x8 Tb disks
- New server