Scalability and performance

[peterk]

Hello,

I would like to use FCS in a big project where more then 10.000 assets is planned to be in a FCS Library. I know FCS uses postgreSQL running on localhost as the DB engine. I would like to know:
1. What are some "standard" limitations of postgreSQl running on one dual CPU Xserve ? (How many clients, how many assets, etc.)
2. Is there any way how to use a separate machine with postgreSQL running on it and rest of FCS running on main machine ? I mean, if I could build a external postgreSQL server(s) and if I could connect FCS to it.
3. What about redundancy? Is there any known setup how to run two (three) FCServers in a parallel with automatic DB synchronization and some failover mechanism ?

Thank you.

Peter

[Tim Burton]

All of the above is possible, however it could be causing yourself ball ache unneccisarily. 10,000 really isnt that much when comapred to systems in other sectors.

1 Box FCSvr is essentially doing:
• DB managment and lookups
• Data Movement
• Encoding
• NAS for proxies
• NAS for media to non Xsan clients
• OD Authentication

So i would look to be moving the tasks that can be moved without hacks onto other servers (italic items need to stay on the FCSvr), with a XSAN backbone between and possibly the clients. With one of the servers as a warm standby. For example:

Server 1 - FCSvr
• DB managment and lookups
• Data Movement[/list]

Server 2 - MDC
• XSAN Controller (primary)
• NAS for proxies & non Xsan clients via 'Edit in place' (load balanced via DNS)
• Compressor (debatable)

Server 3 - BMDC & Compressor
• XSAN Controller (secondary)
• Compressor
• NAS for proxies & non Xsan clients via 'Edit in place' (load balanced via DNS)
• FCSvr Loaded but inactive
• HDD with FCSvr backups to restore from in event of server 1 failing

Server 4/5/6 - Compressor
• More comrepssor hoursepower should you feel you need it

Hope thats not too obvious an answer, and I love a good tinker, but I think seperating FCSvr from its DB with a custom install would cause issues down the line with upgrades and support. I have built systems where Linux boxes are the MDCs and doing all the heavy NAS lifitng.

Tim

[CharlieM]

Following up on the question: has Apple published technical specs on how many assets are supported by FCSVR? Couldn't find any online or in the documentation.

If this is a limitation of the PostgreSQL database, it would be great to know the limitations to answer questions about scalability.

[soward]

I am not that familiar with the inner workings of FCS, but postgreSQL is most likely not a limiting factor. Here are its core limitations (from their site):

Limit Value
Maximum Database Size Unlimited
Maximum Table Size 32 TB
Maximum Row Size 1.6 TB
Maximum Field Size 1 GB
Maximum Rows per Table Unlimited
Maximum Columns per Table 250 - 1600 depending on column types
Maximum Indexes per Table Unlimited

[BenT]

We have recently found that Final Cut Server with a large number of assets performs MUCH better after making the following Postgres tweaks:

Use root to edit:
/var/db/FinalCutServer/data/postgresql.conf

Backup the database, stop FCSVR, ensure POSTGRES processes stopped.
Change the .CONF file values:

shared_buffers -> 256MB
work_mem -> 128MB
maintenance_work_mem -> 128MB

Restart FCSVR (just press START in the System Prefs pane) and you should find search times are much better.