Increase CPU and memory resources | Scale | Northflank Application docs

v1

Overview
Getting started
- Introduction to Northflank
- Link your Git account
- Create a project
- Build and deploy your code
- Set up a pipeline
- Add and verify a domain
Production workloads
- Get production-ready on Northflank
- Release for production
- Persistent storage in production
- Production operations
Deploy on Northflank
Migrate from Heroku
Pricing on Northflank
How-to guides
Build
- Build your code on Northflank
- Build code from a Git repository
- Build code from a self-hosted VCS
- Inject build arguments
- Build with a Dockerfile
- Build with buildpacks
- Pull images from Northflank
Run
- Run containers and micro-services on Northflank
- Run an image continuously
- Run an image once or on a schedule
- Run an image from a container registry
- Save registry credentials
- Change deployment source
- Inject runtime variables
- Deploy to a region
- Access running containers locally
- Override command or entrypoint
Release
- Continuous integration and delivery on Northflank
- Manage CI/CD
- Create a pipeline and release flow
- Configure a release flow
- Set up a preview environment
- Run and manage releases
- Run migrations
Infrastructure as code
- Infrastructure as code on Northflank
- Create a template
- Write a template
- Run a template
- Share a template
- GitOps on Northflank
- Use GitHub Actions with Northflank
Observe
- Observability on Northflank
- See builds
- Monitor containers
- View logs
- View metrics
- Configure health checks
- Configure notification integrations
- Set infrastructure alerts
- Configure log sinks
- Tag workloads and resources
Scale
- Scaling your services on Northflank
- Scale replicas/instances
- Increase CPU and memory resources
- Increase storage
- Autoscale deployments
Databases & persistence
- Stateful workloads on Northflank
- Deploy a database
- Connect database secrets to workloads
- Access a database
- Scale a database
- Configure addons for high availability
- Database observability and monitoring
- Backup, restore, and import data
- Upgrade a database
- Add a persistent volume
- Deploy databases and storage on Northflank
- Migrate your data to Northflank
- Integrate with a database provider
  - Integrate Mongo Atlas with Northflank
Network
- Networking on Northflank
- Expose your application
- Configure ports
- Set IP policies
- Configure basic authentication
- Enable multi-project networking
- Use Tailscale
Secure
- Security on Northflank
- Inject secrets
- Upload secret files
- Manage secret groups
- Manage API tokens
- Enable single sign-on and multi-factor authentication
Domains
- Domains on Northflank
- Add a domain to your account
- Link a domain to a port
- Remove a domain
- Use a CDN
- Wildcard domains and certificates
- Domain registrar guides
Collaborate
- Collaborate on Northflank
- Create a team
- Manage an organisation
- Manage Git integrations
- Using role-based access control
- Grant API access
Cloud providers
- Using other cloud providers with Northflank
- Add your cloud account to Northflank
- Create a Kubernetes cluster with Northflank
- Manage and use your Kubernetes cluster with Northflank
- Deploy your workloads to specific node pools
Billing
- Pricing on Northflank
- Add a card
- Monitor spending
- View invoices
- Pay an invoice
- Add your tax ID
API & CLI
Use the API
Use the CLI
Use the JavaScript client
Forwarding
Execute commands
Log tailing
Retrieve metrics

Application API & CLI

On this page

Increase Docker SHM size
Next steps

Scale /

Increase CPU and memory resources

You can increase the proportion of CPU and memory dedicated to a service on the resources page, available for all Northflank services.

Increasing the CPU share, or assigning one or multiple CPUs, and memory size can be useful if builds are taking a long time or if your service is handling intensive tasks.

Selecting the compute plan for a deployment service in the Northflank application

See Northflank pricing plans for CPU and memory resources.

Increase Docker SHM size

You can configure the amount of available memory-backed disk space available to /dev/shm from the resources page of combined services, deployment services, and jobs. The default SHM size assigned to containers is 64MB.

Using /dev/shm/ can significantly increase performance over using /tmp for I/O intensive processes.

Writing to /dev/shm will incur memory usage of the container. With insufficient container resources this may lead to out-of-memory conditions and crash your container.

Next steps

Scale replicas

Easily increase or decrease the amount of replicas to run depending on demand for your service.

Increase storage

Increase the persistent storage available for your replicas.

© 2024 Northflank Ltd. All rights reserved.

northflank.com Terms Privacy feedback@northflank.com