I'm using Links Non-SQL (2):
- 7,686 links
- 43 categories
- no added fields
- 75 minutes to build (once daily) via cron
- typical search time of 2-5 sec
- no database corruption or crashes
How many links are possible has been put at 5,000 (1 MB) by Eliot. And that is probably a good rule of thumb for flatfile databases. Sooner or later you will have to upgrade to Links SQL - or at least split your links database. However, the upper limit will vary according to whether you are hosted virtually or dedicated (I'm dedicated so I have more cpu resources available to handle Links). It will also vary according to your server specs (e.g., RAM) and other processes working in the background - especially if you are hosted virtually.
Dan
- 7,686 links
- 43 categories
- no added fields
- 75 minutes to build (once daily) via cron
- typical search time of 2-5 sec
- no database corruption or crashes
How many links are possible has been put at 5,000 (1 MB) by Eliot. And that is probably a good rule of thumb for flatfile databases. Sooner or later you will have to upgrade to Links SQL - or at least split your links database. However, the upper limit will vary according to whether you are hosted virtually or dedicated (I'm dedicated so I have more cpu resources available to handle Links). It will also vary according to your server specs (e.g., RAM) and other processes working in the background - especially if you are hosted virtually.
Dan
