What is the range of concurrent connections do you wish to test?
I have a database with over 48 GB of data in it, with about 27GB in one
I am running on Kubuntu 8.10 on a 32 bit machine, with only 3 GB of ram.
I can set up bash scripts that connect via isql and run a series of
I am using 16k block sizes, but I can try smaller sizes if it is thought
Personally, I would love to see a 32 and 64k block size implemented to
have the Firebird block size match up with the Raid block size and the
Filesystem block size.
I don't know what work would be involved but larger block sizes have
major impacts on speed in larger database configurations.
I am also testing the database cross-connect abilities of 'execute
statement', very nice and will simplify our schema dramatically.
Has anyone ever suggested the ability to create an in-memory array based
upon a table structure? Ie, declare variable FOO based upon table
It would be a multidimensional array with different data/column types
depending upon the column.
Benefits would include
No need to declare a series of variables in order to store the
results from a select, as a single variable would do the job.
The ability to pass a specific result set back and forth between
procedures without tons of parameters needing to be declared.
The ability to address a complex array of values randomly without
having to always iterate through a result set.
The stored procedure language code would be far easier to read.
Currently, variables can be defined based upon the definition of a
column within a table or by domain, and arrays do exist.
I don't know if this idea has been addressed already, but, I can see
benefits to the work, but I have been so busy over the years that I
don't even know how to suggest the idea properly.
Is there an existing test suite that I can download and try on on
various different hardware/server platforms?
On Fri, 2008-11-14 at 20:22 +0300, Alex Peshkov wrote:
> On Friday 14 November 2008 20:02, Dalton Calford wrote:
> > I am dedicating some time to testing this alpha.
> > I am wondering if someone can give me a heads up as to what has been and
> > has not been tested so far?
> > Where are the areas of concern?
> The most problematic-possible area in 2.5 is simultaneous access to database
> in superclassic mode. I think this is what requires specially careful
> > What is the state of the code - is it in a feature freeze or are new
> > features still being added?
> New features may be added before beta1. And yes, some features will be added
> in 2.5 beta1.
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel