| |
__________________________________________________
Limits
AxleBase is designed and engineered to the following limits.
| _______________ | _____________ | ___________ | ___ |
| object | elements | limit | note |
| | | | |
| column | bytes | 2 billion | |
| | | | |
| row | bytes | 2 billion | |
| | columns | 2 billion | |
| | | | |
| table | rows | 20 quintillion | [1] |
| | bytes | 20 exabytes | [1] |
| | computers | 10 billion | [3] |
| | DASD | 10 billion | [3] |
| | | | |
| database | tables | 20 million | [4] |
| | virtual tables | 20 million | |
| | files | no limit | |
| | bytes | no limit | [5] |
| | | | |
| virtual table | per database | 20 million | |
| | concatenation | no limit | |
| | | | |
| domain | databases | no limit | |
| | | | |
| installation | domains | no limit | |
| | databases | no limit | |
| | instances | no limit | |
| | | | |
| name length | characters | 80 | |
| | | | |
| index | columns | no limit | |
| | bytes | no limit | [7] |
| | rows | no limit | [7] |
| | | | |
| SQL statement | columns | no limit | |
| | characters | no limit | |
| | | | |
| query return | rows | no limit | [6] |
| | bytes | no limit | [6] |
| | | | |
| concurrency | clients | no limit | [8] |
| | | | |
| operating system | AxleBase | Windows | |
| | | 95 | |
| | | NT | |
| | | 98 | |
| | | 2000 Pro | |
| | | 2000 Server | |
| | | XP Pro | |
| | | Vista | [9] |
| | database | no limit | [10] |
| | | | |
| system distribution | network | no limit | [11] |
| | | | |
Quantities are rounded to speed comprehension, and are rounded down to avoid deceit.
The 'no limit' may indicate one or more of the following :
A limit has not been conceived.
An engineering specification is not yet established.
Variables involved preclude precise specification.
The value may surpass practical requirements of Mankind's current state.
The value may surpass current practical limits of computer technology.
Footnotes follow:
| ____ | _____________________________________________________ |
| key | comment |
| | |
| [1] |
20 exabytes, or 20 quintillion, or 20,000,000,000,000,000,000, or 2 x (10^19). |
| [1] |
Bytes and rows are limited by the same mechanism. The
one that reaches the stated limit first will halt the
expansion of both. |
| [1] |
The internal architecture will allow an increase of thousands of times larger, but that would yield
zetabytes, approaching the rediculously large area of
the planck domain in a single table. |
| [3] |
The number of computers and/or storage devices that can
be used to store each table. The total of the two cannot
exceed the stated number. |
| [3] |
Hardware, operating systems, and networks that house data objects in a database are transparently managed
and queried by AxleBase. |
| [4] |
The number of tables in each database is limited to
the number of table configuration records that can be
stored in the table table, which is limited to two
billion bytes. The configurations are variable length
of maybe a few hundred bytes. |
| [5] | (Bytes per table) times (tables per database) yields 4 x (10^25)
bytes. |
| [6] |
AxleBase normally uses RAM to build queries as do conventional
systems, but a switch can tell him to use the computer's
DASD. |
| [7] |
Index size can impact performance. The maximum size is
certainly not recommended. |
| [8] |
Although he can do it, high concurrency is not an AxleBase
objective. He is primarily a workhorse for carrying massive loads up to any conceivable size. See the design
objectives and concurrency tests. |
| [9] | Not tested on 7, 2003 Server, and 2005 Server. |
| [10] |
Since AxleBase can distribute data objects, his databases
may be placed on any computers that can express a Windows
file system including mainframes, Linux, Unix, etc. |
| [11] |
This addresses the use of AxleBase in his distributed form.
Any network will suffice as long as it is totally transparent, it does not interfere with his operations, and he can add syslink to the network protocol stack. |
| | |
Errors :
The simplicity and small size of this report hides the huge amount of research and thought that went into it. Notification of any error in it will sincerely be appreciated.
__________________________________________________
|
|
