leeter
HADOKEN!! Solving all Problems
A few things that may or may not be well received:
1. use asp.net as it's currently the fastest thing on the net and precompiled and can be run on freeBSD using mono
2. vectorize all non-user created graphics including banners, this makes these much smaller and reduces bandwidth load and puts the load on the client machine
3. normalize the database as much as possible without being lossy say third normal form, yes this means you'll have to do more joins in queries but overall it will increase the flexibility of the database and should ultimately make it faster.
4. use precompiled views when ever possible inside the database, because they're precompiled they run MUCH faster than straight queries and will increase overall response time.
5. rename all pictures using a unique id in asp.net this is a GUID, this provides a nice name for the picture on the disk because, overall people are not creative and are very likely going to reuse names. Resave the originals as png's to disk, NOT in the database, and create a thumb at upload time, saved also to disk as a jpg for ease of bandwidth.
Thats all for now take what you will
1. use asp.net as it's currently the fastest thing on the net and precompiled and can be run on freeBSD using mono
2. vectorize all non-user created graphics including banners, this makes these much smaller and reduces bandwidth load and puts the load on the client machine
3. normalize the database as much as possible without being lossy say third normal form, yes this means you'll have to do more joins in queries but overall it will increase the flexibility of the database and should ultimately make it faster.
4. use precompiled views when ever possible inside the database, because they're precompiled they run MUCH faster than straight queries and will increase overall response time.
5. rename all pictures using a unique id in asp.net this is a GUID, this provides a nice name for the picture on the disk because, overall people are not creative and are very likely going to reuse names. Resave the originals as png's to disk, NOT in the database, and create a thumb at upload time, saved also to disk as a jpg for ease of bandwidth.
Thats all for now take what you will
