On 12/14/11 20:02, Carlos H. Cantu wrote:
One year ago, when I was discussing this with Vlad, I did small
Delphi app using ZeosDB components to measure speed between FB and
MySQL similar databases with same data, hosted on remote computer and
acessing by adsl connection. Results proved that
(gdb) print *attachment
Não é possível acessar a memória no endereço 0x732b9040
Does such dirty attachment arrive in any test or only in some specific?
--
10 Tips for Better Server Consolidation
Server
Yes, but note that now my link is 20Mbits/s download:
1 *** Esgotado o tempo limite do pedido.
210 ms11 ms 7 ms bd232401.virtua.com.br [189.35.36.1]
3 8 ms11 ms11 ms bd07980b.virtua.com.br [189.7.152.11]
410 ms12 ms10 ms
All,
CORE-3238 is the problem related to UUIDs version and reserved bytes
which we're not respecting.
Note that in Windows, we generate UUIDs with a WinAPI function so it
generates correct numbers, but in POSIX we just generate random data.
1) So from a POV, we may say our GEN_UUID is correct
On 15/12/2011 15:04, Leyne, Sean wrote:
Adriano,
CORE-3238 is the problem related to UUIDs version and reserved bytes which
we're not respecting.
Note that in Windows, we generate UUIDs with a WinAPI function so it
generates correct numbers, but in POSIX we just generate random data.
1)
Note that in Windows, we generate UUIDs with a WinAPI function so it
generates correct numbers, but in POSIX we just generate random data.
For Windows users this binary representation is also wrong now, cause
reserved bits is not documented in it.
You wrote that the WinAPI function
On 15/12/2011 16:46, Leyne, Sean wrote:
Note that in Windows, we generate UUIDs with a WinAPI function so it
generates correct numbers, but in POSIX we just generate random data.
For Windows users this binary representation is also wrong now, cause
reserved bits is not documented in it.
You
As I said before, ext4 performance with FW=ON is much slower than ext3,
but I now found something new.
I've verified that with FB 2.5, TCS times was ok (0s - 3s), and only
with FB 3 they are very bad (first test takes 16s, then 12s, 8s, 7s, 7s,
etc)
What I found is that:
Times was bad
On 15-12-2011 18:11, Vlad Khorsun wrote:
As I said before, ext4 performance with FW=ON is much slower than ext3,
but I now found something new.
I've verified that with FB 2.5, TCS times was ok (0s - 3s), and only
with FB 3 they are very bad (first test takes 16s, then 12s, 8s, 7s, 7s,
etc)
On 12/15/11 15:54, Carlos H. Cantu wrote:
Yes, but note that now my link is 20Mbits/s download:
1 *** Esgotado o tempo limite do pedido.
210 ms11 ms 7 ms bd232401.virtua.com.br [189.35.36.1]
3 8 ms11 ms11 ms bd07980b.virtua.com.br
So now we're spending time while the database is not even completely
created.
While we can restore previous behavior (put FW ON flag at header page
when database is created but create db file with this flag switched off) i
prefer
to ask - are we really want to maintain this hack ?
11 matches
Mail list logo
