GOING. NUTS.

[protocollie]

Okay, I'm sorta putting out a generic cry for help because I know a lot of people who follow me are super smart and hopefully someone can give me some insight or an avenue to explore that I haven't yet.

I. Hate. SQL. Server. Performance. Tuning.

We're having a problem here. We have a file storage service in our system that consists of two tables, one

Comments

[breakspire]

that icon is from a dirty picture o.o

[protocollie]

nawh

[origamigryphon]

yeh

[jpsqueetis]

I tried programming, but I never was any good at it. It looks like Chinese to me. :P

[skippyfox]

Have you tried checking your megabytes?

[lupine_fox]

It's the gigabytes stupid!

[blitzneko]

shame you can't cut up the data to be processed in to smaller clusters and chunks.... Otherwise mabye you need a better way of deleted/modifing select data, and somehow get it to play nice with the SQL....

[protocollie]

Well we actually write it in chunks, but the thing is the overhead of concatenating all those chunks either on the SQL side or in memory on the database server is pretty significant.

We actually think we figured it out and it makes sense, since SQL wasn't showing it was misbehaving at all, this might actually be a resource issue. It seems like it's a combination of memory pressure and disk IO speed.

[lupine_fox]

Cluster your chunks and then chunk the clusters and you'll stop the total cluster-chunk.