I'm pritty new at SQL so their may be something else I could do to increase speeds? May be a look at C ???
I have seen
slow SyBase SQL systems in practice. Multiple Oilfields and Oil plattforms with a central SQL database where every little tag on the plattform had a tag in the database.
In one of the above mentioned posts I wrote:
You have to know the following:
1. Everything digital is a bitstream (dynamic or static).
2. In large projects you have to figure out bottlenecks.
- Memory.
- Connections
- Processor speed.
- Lenguage speed ((Assembler), C is is faster than C++). But some say
that processor speed is much cheaper than programming time. There
is a tradeoff.
- Disk capacity.
3. Generally, minimalise connections.
4. Use distributed processing (on multiple servers) only in really large
projects.
5. I agree, operate on the the data(base) structure where possible.
6. Do you use 1 --> n relations or k --> n relations.
7 Use (memory) references (pointers) in stead of copies where possible.
9. Last but not least, the algorithm and datastructures you use are
important. E.g. some sorting algorithmes run in n*log(n) time, while
others run in linear time, e.g. counting sort and radix sort in some cases.
A lot of databaseoperations are sorting or sorting related, so be sure that
you use the most effective algorithm.
http://www.sitepoint.com/forums/showthread.php?t=313377
Here:
http://www.acomputerportal.com/
http://www.agreatportal.com/index.html
some examples of the portals TrafficProducer builds. The web is increasing exponentially. I do not know how he indexes / archives sites and / or pages.
Depending on storage and
use, the burden on the system may increase very fast. It is also difficult to foresee future usage in the digital world that is (after all) in its childhood.
Effective digital logistics
http://multifinanceit.com/it/logistics/logistics.htm is becoming increasingly important.