Hi Gábor!
df -Th | grep ram
tmpfs tmpfs 15G 820M 15G 6% /ramdisk
András
-Original Message-
From: Gabor Boros
Sent: Sunday, October 14, 2018 10:26 AM
To: firebird-devel@lists.sourceforge.net
Subject: Re: [Firebird-devel] Meltdown and Spectre
2018. 01. 09. 10:52
2018. 01. 09. 10:52 keltezéssel, Omacht András írta:
The database file and the tmp directory located on ramdisk.
What was the filesystem of the ramdisk? Tmpfs?
Gabor
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
Anything doing a lot of user-mode to kernel-mode transitions is affected
the most. That's why i.e. IO intensive code suffers more than just
computations.
--
Mgr. Jiří Činčura
https://www.tabsoverspaces.com/
On Wed, Jan 10, 2018, at 17:47, Carlos H. Cantu wrote:
> I saw a performance comparison (u
I saw a performance comparison (using comercial benchmarks tools, not
specific for databases) and the most impact seems to be on Disk (even
SSD), followed by RAM and CPU. The only area that isn't impacted seems
to be GPU.
[]s
Carlos
http://www.firebirdnews.org
FireBase - http://www.FireBase.com.br
10.01.2018 18:43, Leyne, Sean пишет:
Tests are different, so results cannot be compared "as is".
I appreciate that the tests are different, I was commenting on the relative
performance impact.
Slowdown mostly depends on % of syscalls. R/O vs R/W tests would show
different relative impact
xt time...)
I'm 100% sure this is not a general test procedure, which maybe was run on
PostgreSQL.
András
-Original Message-
From: Leyne, Sean [mailto:s...@broadviewsoftware.com]
Sent: Wednesday, January 10, 2018 4:26 PM
To: For discussion among Firebird Developers
Subject: Re:
> 10.01.2018 18:25, Leyne, Sean wrote:
> >
> > It is most interesting that FB's post-patch numbers show a much larger
> impact (~36% slower) than the Postgres results (~24%).
>
> Tests are different, so results cannot be compared "as is".
I appreciate that the tests are different, I was comment
10.01.2018 18:25, Leyne, Sean wrote:
It is most interesting that FB's post-patch numbers show a much larger impact
(~36% slower) than the Postgres results (~24%).
Tests are different, so results cannot be compared "as is".
Dmitry
András,
> -Original Message-
> From: Omacht András [mailto:aoma...@mve.hu]
> Sent: Wednesday, January 10, 2018 9:08 AM
> finally we choose the easiest way, backup the system and update it to
> Debian SID.
>
> # uname -a
> Linux firebirdtest 4.14.0-3-amd64 #1 SMP Debian 4.14.12-2 (2018-01
[mailto:s...@broadviewsoftware.com]
Sent: Tuesday, January 9, 2018 4:35 PM
To: For discussion among Firebird Developers
Subject: Re: [Firebird-devel] Meltdown and Spectre
András,
> We've done some test runs with the 'old' kernel (linux-image-4.9.0-4-
> amd64) and the 'new
Here are a few details on Linux related distros
https://lwn.net/Articles/742999/
Also Intel already prepared microcode patches and they push it trough OS
update channels
https://hothardware.com/news/microsoft-windows-10-pcs-haswell-intel-cpus-significant-slowdowns-post-spectre-patch
On Tue, Jan
> The performance impact of the recent fixes hinge, mainly, on whether
> the host OS/kernel has PCID support.
First of all, the CPU must support PCID.
> PCID support was only added to linux kernel 4.14, released November
> 2017.
... and only to recent CPUs.
Michal Kubecek
>AFAIU, all that I can get from that is some (kilo)bytes from random
> memory area. Mostly
> it would be random binary garbage which can be hardly interpreted as
> something useful.
Not exactly. Mostly you get some uninteresting garbage. But with enough time
(matter or hours) you will get
Here are some numbers based on pgbench:
https://www.phoronix.com/scan.php?page=article&item=linux-415-x86pti&num=2.
--
Mgr. Jiří Činčura
https://www.tabsoverspaces.com/
On Tue, Jan 9, 2018, at 16:34, Leyne, Sean wrote:
> András,
>
> > We've done some test runs with the 'old' kernel (linux-image-4
András,
> We've done some test runs with the 'old' kernel (linux-image-4.9.0-4-
> amd64) and the 'new' one (linux-image-4.9.0-5-amd64).
>
> No. of tests: 6014
> No. of result checks: 253555 (checking column values, stored procedure
> results, etc.)
>
> Average running time on 4.9.0-4: 466 secs
09.01.2018 12:44, Mark Rotteveel wrote:
The problem with meltdown and spectre is that it could potentially allow you to gather
information that the exploited process would normally not be able to access.
AFAIU, all that I can get from that is some (kilo)bytes from random memory area. Mostly
On 9-1-2018 12:40, Dimitry Sibiryakov wrote:
09.01.2018 12:36, Mark Rotteveel wrote:
it can be exploited by any code running local on your machine. So
anything on that machine that could have a remote code execution
vulnerability, or just a plain malicious update, could then exploit it.
An
09.01.2018 12:36, Mark Rotteveel wrote:
it can be exploited by any code running local on your machine. So anything on that machine
that could have a remote code execution vulnerability, or just a plain malicious update,
could then exploit it.
Anything that can have such vulnerability don't n
On 9-1-2018 11:25, Sergey Mereutsa wrote:
Hi!
Just for your information - if this is your own dedicated server and you
do NOT run untrusted code on it (which can potentially steal your data
and send to someone) - you can safely disable this patch.
Just because you do not defend yourself from
.
András
From: Sergey Mereutsa [mailto:s...@dqteam.com]
Sent: Tuesday, January 9, 2018 11:25 AM
To: For discussion among Firebird Developers
Subject: Re: [Firebird-devel] Meltdown and Spectre
Hi!
Just for your information - if this is your own dedicated server and you do NOT
run untrusted code on it
On Tue, 9 Jan 2018 12:25:24 +0200 Sergey Mereutsa wrote
>
> Both vulnerabilities are LOCAL :)
>
Your server also has to be air-gapped from the internet and all its
clients must also be air-gapped from the internet.
If there is any connection to the outside world then all bets are off
as one f
Hi!
Just for your information - if this is your own dedicated server and you do
NOT run untrusted code on it (which can potentially steal your data and
send to someone) - you can safely disable this patch.
Just because you do not defend yourself from yourself :)
Both vulnerabilities are LOCAL :)
On Tue, 9 Jan 2018 09:52:59 + Omacht András wrote
>
> Average running time on 4.9.0-4: 466 secs (7 mins 46 secs)
> Average running time on 4.9.0-5: 635 secs (10 mins 35 secs)
That is a massive hit.
Has anyone had a chance to run tests on AMD kit?
Paul
--
Paul Reeves
http://www.ibphoen
Hi!
Just for the shake of information.
Our test system running on Debian 9.3.
processor : 7
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Xeon(R) CPU E5420 @ 2.50GHz
stepping: 6
microcode : 0x60b
cpu MHz :
24 matches
Mail list logo