On Aug 28, 2008, at 3:19 AM, [EMAIL PROTECTED] wrote:
>> Is there a performance hit assosiated with manifest typing?
>
> I'm not sure about performance, but I assume that static typing
> might reduce memory usage (especially with small caches). Internally
> every type in sqlite is stored in s
> Is there a performance hit assosiated with manifest typing?
I'm not sure about performance, but I assume that static typing might reduce
memory usage (especially with small caches). Internally every type in sqlite is
stored in structure that takes 64 bytes (little more on 64 bit systems).
Dif
On Wed, Aug 27, 2008 at 03:50:56PM +0100, Hardy, Andrew wrote:
> Is there any way to log conversions to highlite any issues that would
> have been hilighted by failure with strict typing?
If the conversions are nicely isolated into functions (static and
otherwise) could use the DTrace 'pid' provid
The Sqlite manifest typing integrates nicely with scripting languages
which use similar strategies. Where such integration is not required
and there is a well defined application such as an embedded system,
particularly with a slower processor, a static typing model would be
advantageous in ma
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Dennis Cote
> Sent: 27 August 2008 15:45
> To: General Discussion of SQLite Database
> Subject: Re: [sqlite] Manifest Typing performance impact?
>
> Hardy, Andrew wrote:
>
I made some changes to Sqlite to stop the automatic type conversions.
The performance improvement was not significant. My reason was not to
avoid the performance overhead but to prevent the use of floating point
where it would raise precision problems.
My suggestion would be not to worry about
D. Richard Hipp wrote:>
> I was going to guess the opposite - that manifest typing reduces
> overhead. (But as Dan pointed out - nobody will know until somebody
> generates a version of SQLite that uses static typing and compares the
> performance.)
>
I agree with Dan on this point.
> The
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dennis Cote
Sent: 27 August 2008 15:45
To: General Discussion of SQLite Database
Subject: Re: [sqlite] Manifest Typing performance impact?
Hardy, Andrew wrote:
>
> Is there a performance hit assosiated with manifest typing?
>
I
On Aug 27, 2008, at 10:45 AM, Dennis Cote wrote:
> Hardy, Andrew wrote:
>>
>> Is there a performance hit assosiated with manifest typing?
>>
>
> I'm sure there is since sqlite must track the type of each data item
> as
> well as its value. But in reality this overhead is quite small.
>>
I was
Hardy, Andrew wrote:
> Is there any way to log conversions to highlite any issues that would
> have been hilighted by failure with strict typing?
>
Not that I am aware of.
Dennis Cote
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.
Hardy, Andrew wrote:
>
> Is there a performance hit assosiated with manifest typing?
>
I'm sure there is since sqlite must track the type of each data item as
well as its value. But in reality this overhead is quite small.
> Is it right that although info on the sqlite site suggests there is
On Aug 27, 2008, at 4:03 PM, Hardy, Andrew wrote:
> Is there a performance hit assosiated with manifest typing?
Yes. No. Possibly. Difficult to tell unless somebody creates
and optimizes a version of sqlite that does not do manifest
typing.
> Is it right that although info on the sqlite site su
Is there a performance hit assosiated with manifest typing?
Is it right that although info on the sqlite site suggests there is an
avilable mode that supports strict typring, this is not infact the case?
If there is a performance hit, what are the best ways to minimise this?
And is there any wa
Is there a performance hit assosiated with manifest typing?
Is it right that although info on the sqlite site suggests there is an
avilable mode that supports strict typring, this is not infact the case?
If there is a performance hit, what are the best ways to minimise this?
And is there any
14 matches
Mail list logo
