Appian Knowledge Center

Certified Senior Developer

Appian Content Management (Knowledge Center) . Which Appian engine takes care of searching and retrieving documents from KB when provided with Document id / document uuid.

does the volume of data impact performance of Appian? by any means? (we have close to 30 Lakh documents in KB).

Can you please share links to read and understand more on architecture around Appian Content management (KB)

  Discussion posts and replies are publicly visible

Parents
  • 0
    Certified Lead Developer

    That's the content engine.  You have generally only 1 per Appian environment, and it can be a problem if you have a tremendous number of objects.  In your case, you might be starting to see some very small effect on the performance of the content engine.  At about 5 to 10 times your current level of documents, you might start to see some serious churn.

    I would advise, depending on how many documents you ultimately expect to have stored, to find some means of removing outdated ones and placing them in a more purpose-build document repository, or working out long-term retention policy so old ones may be archived elsewhere or deleted.  If that's not viable, and you are expecting to eventually reach 5 or 10 times as many docs, you may want to consider upgrading to multiple content engines.

    In a former project our BIG problem was the number of folders we generated.  It was around 20 million Content objects where we started having real problems.

Reply
  • 0
    Certified Lead Developer

    That's the content engine.  You have generally only 1 per Appian environment, and it can be a problem if you have a tremendous number of objects.  In your case, you might be starting to see some very small effect on the performance of the content engine.  At about 5 to 10 times your current level of documents, you might start to see some serious churn.

    I would advise, depending on how many documents you ultimately expect to have stored, to find some means of removing outdated ones and placing them in a more purpose-build document repository, or working out long-term retention policy so old ones may be archived elsewhere or deleted.  If that's not viable, and you are expecting to eventually reach 5 or 10 times as many docs, you may want to consider upgrading to multiple content engines.

    In a former project our BIG problem was the number of folders we generated.  It was around 20 million Content objects where we started having real problems.

Children
No Data