powered by CADENAS


Manual More information

  • Notes on reliability and performance/caching

    Notes on performance: three-step


    • License service

      Backup server strategy implemented by CADENAS

      Details on this can be found under Section, “ "Connected servers" dialog area ”.

    • PARTapplicationServer

      Standard Windows Watchdog

      Setting up PARTapplicationServer as service is advantageous, because it is automatically started at start of the server and Windows mechanisms for monitoring the stability (e.g. restart at crashes) are used. (Restart delay can be adjusted via registry.)

      On this see Section, “Set up PARTapplicationServer as service ”.

    • Database

      PLINKDB is mostly running on an already existing DB server whose availability is guaranteed by the customer (DB specific strategy)

  • Pool directory

    There are some possibilities for the storage location of the pool directory:

    • Local pool directory

    • Pool directory on the server, but with different share than CADENAS_DATA



    • CADENAS_DATA on a dummy directory. In this case the pool directory may point to the server.



    The only important thing is that the location of the pool directory is not under CADENAS_DATA; because then the RemoteFileSystem is responsible for the pool directory and thus it is ReadOnly.

  • Ports settings:

    Ports for PARTapplicationServer and SearchServer, configured in the configuration files differ by default, so that it is possible to drive parallel on one server, which could happen in the changeover phase.

  • Slowed down search when using a virtual disk

    When testing on a virtual machine you have to consider, that the C disk on the server is not really local, but rather is in the network. (When testing on a real C disk the speed is possibly higher.)

    When caching is used, all search indices are saved on the PARTapplicationServer. This makes sense, because accessing a local resource is faster.

    Using a VM the process differs: Caching happens from the net into the net and then parts are loaded from there. This could act as a brake.

    Better use an ESX host with local disks, still better an ESX host with local SSDs. In this way search times can be reduced again, especially if a search results in as many parts that they do not fit into the memory. Furthermore then there is no network bottleneck.