🔧

Performance

The nLogin can be configured to improve performance. Check out the following recommendations:
Monitor process usage
The timing of nLogin's main resources can be tracked in real time via the /nlogin monitor command.
Example of nLogin monitoring.
Change the hashing algorithm 
The password encryption process is one of the most costly processes in nLogin. 
By default, nLogin uses BCRYPT, but you can change this in config.yml.
#     ___                                    _
#    / _ \__ _ ___ _____      _____  _ __ __| |___
#   / /_)/ _` / __/ __\ \ /\ / / _ \| '__/ _` / __|
#  / ___/ (_| \__ \__ \\ V  V / (_) | | | (_| \__ \
#  \/    \__,_|___/___/ \_/\_/ \___/|_|  \__,_|___/
#
# Password settings.
passwords:
  hashing:
    # Define here what type of hash algorithm nLogin will use.
    # Valid values [ARGON2D, ARGON2I, ARGON2ID, BCRYPT, BCRYPT2Y, MD5, PBKDF2, SHA256, SHA512].
    algorithm: "BCRYPT"
​
    # Bcrypt settings.
    bcrypt:
      rounds: 10
​
    # Argon2 settings.
    argon2:
      iterations: 10
      memory: 64
      parallelism: 1
Hint! If you are not satisfied with the processing cost of BCRYPT, we recommend using SHA512.
Disable encryption with secret keys 
Encryption using secret keys for proxies can require a lot of processing. 
The encryption process used can be costly for your server! 
We recommend that you always prefer to use the proxy server and the backend server on the same machine.
*If you use shared hosting, opt for network plans or split plans. If the host does not offer this service, ask them via tickets to migrate both servers (proxy and backend) to the same node (extra service fees may apply).

Tutorials - Previous

Migrating to nLogin

Next - Development

API Migration

Last modified 1yr ago