MySQL vs Flat Files what's my limit?

[too much information]

I've had a rough two weeks now and to top it off I'm on a shared MySQL server and someone locked it up, so I'm considering making some changes to some of my smaller sites from MySQL to Flat Files so they will be independent of any future database issues but I don't have much experience with the limitations of this method.

So what is the max as far as XML style flat files go before I start to hit performance issues?

[Brett_Tabke]

you are soaking in a directory with about 30k files in it. The google forum has about 50k files in it. The IP directory here, can have as many as 50k files that get updated and purged every 20mins

I'd start to worry about 150k...

do not attempt this under windows... where performance will be a major issue.

[too much information]

Thanks Brett, that's a big help. Does this also provide a little more protection as far as code injection goes. I know it would prevent any SQL injections obviously, but overall is this a little safer way to go with storing data?

[penders]

I tend to use flat files quite a bit. In fact I'm probably from the other camp... should I perhaps be using a SQL DB? But to be honest, with 1000's of records (read) performance has been good.

File management could be more of an issue, however, particularly if multiple users could potentially edit the same file/record...?

[coopster]

I'm on a shared MySQL server and someone locked it up

(emphasis added)

I realize I am stating the obvious here but I feel it needs mentioning -- your issue is not in where to store the data in regards to filesystem/RDBMS but in hosting services. If you are running into issues now in regards to mere database services, it is going to get worse (think application/code level). You might consider investing your time/money in a different platform/provider at this point rather than programming changes/modifications. Just a thought ...