[Date Prev][Date Next] [Chronological] [Thread] [Top]

RE: (ITS#8972) Performance/freezing issues using NTDLL onWindowsServer on Azure

--_FEED8D1F-4CE2-4DE8-A6B1-1703AFFCC4FC_
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

To follow up to this, after switching to the stable release in node-ldmb, a=
nd running on our servers for several days, I can confirm this definitely d=
oes fix our issues (and ticket can be closed). I=E2=80=99ve submitted a PR =
for getting the correct stable version in node-lmdb, to ensure in this does=
n=E2=80=99t happen for other NodeJS users: https://github.com/Venemo/node-l=
mdb/pull/141=20

I did find a minor issue with setting up the file mapping in the release ve=
rsion, but I will file that separately. And if the NTDLL mapping isn=E2=80=
=99t intended to be merged into a release branch, sounds like there shouldn=
=E2=80=99t be any issues for Windows users that are using LMDB releases.

And to be clear, I am a happy windows user, sorting out versions hardly den=
ts my enthusiasm for LMDB. And thank you again for the help.

Thanks,
Kris

--_FEED8D1F-4CE2-4DE8-A6B1-1703AFFCC4FC_
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="utf-8"

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:sc=
hemas-microsoft-com:office:word" xmlns:m=3D"http://schemas.microsoft.com/of=
fice/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html40";><head><meta ht=
tp-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta name=
=3DGenerator content=3D"Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style></head><body lang=3DEN-CA link=3Dblue vlink=3D"#954F72"><div cla=
ss=3DWordSection1><p class=3DMsoNormal>To follow up to this, after switchin=
g to the stable release in node-ldmb, and running on our servers for severa=
l days, I can confirm this definitely does fix our issues (and ticket can b=
e closed). I=E2=80=99ve submitted a PR for getting the correct stable versi=
on in node-lmdb, to ensure in this doesn=E2=80=99t happen for other NodeJS =
users: <a href=3D"https://github.com/Venemo/node-lmdb/pull/141";>https://git=
hub.com/Venemo/node-lmdb/pull/141</a> </p><p class=3DMsoNormal><o:p>&nbsp;<=
/o:p></p><p class=3DMsoNormal>I did find a minor issue with setting up the =
file mapping in the release version, but I will file that separately. And i=
f the NTDLL mapping isn=E2=80=99t intended to be merged into a release bran=
ch, sounds like there shouldn=E2=80=99t be any issues for Windows users tha=
t are using LMDB releases.</p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>And to be clear, I am a happy windows user, sorting out v=
ersions hardly dents my enthusiasm for LMDB. And thank you again for the he=
lp.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoN=
ormal>Thanks,<br>Kris<o:p></o:p></p></div></body></html>=

--_FEED8D1F-4CE2-4DE8-A6B1-1703AFFCC4FC_--