Hi,

The Flowchart.NET assemblies take about 2 MB of HDD space. Memory and CPU requirements are negligible, unless you are using any of the following:

- link routing -
The routing algorithm builds a grid that needs (diagram.Bounds.Width / rotingOptions.GridSize) * (diagram.Bounds.Height / rotingOptions.GridSize) bytes of RAM. The CPU time required is a polynomial function of the length of the path (in grid pieces) when a path can be found.

- PathFinder -
GetShortestPath is based on a simple floodfill algorithm. The other methods might keep the found paths in memory, and I've seen them using 100s of MBs with very large graphs, and taking minutes to complete.

- layout classes -
The Spring and Anneal layout don't need much additional memory, and the CPU time depends on how many iterations you run. The LayeredLayout needs both much RAM and CPU.

So, the requirements depend on what Flowchart.NET features you are using, and how big your graphs are. If you are using any of the things listed above, try them with the largest diagram you think you'll have in your application, and take a look at the memory and CPU statistics in the task manager window.

I hope that helps,
Stoyan