openldap-bugs

openldap-bugs@openldap.org

1 participants
20967 discussions

(ITS#9165) Paged search results on FreeBSD exceed static buffer
by fjo-openldap＠ogris.de 11 Feb '20

11 Feb '20

Full_Name: Felix J. Ogris Version: 2.4.49 OS: FreeBSD 12.1 amd64 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (80.139.74.144) Hi, I observed that cookies for paged searches against a Windows based Active Directory are up to 1000 bytes in length. print_paged_results() in clients/tools/common.c uses a buf of BUFSIZ chars. BUFSIZ on FreeBSD is only 1024 - see https://svnweb.freebsd.org/base/release/12.1.0/include/stdio.h?view=markup#… Thus, ldapsearch against a Windows AD will print the cookie without a trailing newline, and may expose a security issue if querying an arbitrary LDAP server. Fixing this specific occurrence is easy (e.g. replace buf[BUFIZ] by buf[8192]). What about defining a global LDAP_BUFIZ of at least 8192, since BUFSIZ is used at several locations in the OpenLDAP source tree? BR, Felix

1 0

Re: (ITS#9164) back-monitor returning non-requested attributes
by quanah＠symas.com 06 Feb '20

06 Feb '20

--On Thursday, February 6, 2020 8:47 PM +0000 quanah(a)openldap.org wrote: > This appears to be because they (IMHO) incorrectly SUP monitoredInfo or > monitorCounter Or, thinking on it further, I think this is ok, just not what I expected. I'll close the ITS. ;) --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

(ITS#9164) back-monitor returning non-requested attributes
by quanah＠openldap.org 06 Feb '20

06 Feb '20

Full_Name: Quanah Gibson-Mount Version: 2.4.49 OS: N/A URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (47.208.128.236) The new additions to back-monitor to expose more data from back-mdb are returning unrequested attributes. For example: ldapsearch -x -LLL -H ldap:/// -s base -b "cn=database 1,cn=databases,cn=monitor" "(|(objectClass=monitorCounterObject)(objectClass=monitorOperation)(objectClass=monitoredObject))" monitorCounter monitorOpInitiated monitorOpCompleted monitoredInfo olmMDBPagesMax olmMDBPagesUsed olmMDBPagesFree olmMDBReadersMax olmMDBReadersUsed olmMDBEntries Will return: dn: cn=Database 1,cn=Databases,cn=Monitor monitoredInfo: mdb monitorOverlay: dynlist olmMDBPagesMax: 262144 olmMDBPagesUsed: 629 olmMDBPagesFree: 58 olmMDBReadersMax: 126 olmMDBReadersUsed: 2 olmMDBEntries: 1005 olmDbDirectory: /var/symas/openldap-data/example/ Note that I did not request monitorOverlay nor did I request olmDbDirectory This appears to be because they (IMHO) incorrectly SUP monitoredInfo or monitorCounter

1 0

Re: (ITS#9163) warning: logical not is only applied to the left hand side of bitwise operator
by hyc＠symas.com 06 Feb '20

06 Feb '20

noloader(a)gmail.com wrote: > Full_Name: Jeffrey Walton > Version: 2.4.47 > OS: OS X 10.10 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (100.18.0.145) > > > Hi Everyone. I'm building OpenSLAP 2.4.47 from the release tarball on OS X. > Clang is triggering a warning that may be of interest: Thanks for the report. Appears to be a dup of ITS#8890, which was fixed in master in 2018. Looks like this fell through the cracks for the 2.4 release. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Re: (ITS#9017) Improving performance of commit sync in Windows
by kriszyp＠gmail.com 06 Feb '20

06 Feb '20

--000000000000bdb86d059deaf350 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sorry to keep pestering, but just pinging about this patch again, as I still think this fix could benefit windows users. And at this point, I think I can say we have tested it pretty well, running on our servers for almost a year :). Thanks, Kris On Wed, Sep 18, 2019 at 12:56 PM Kris Zyp <kriszyp(a)gmail.com> wrote: > Checking on this again, is this still a possibility for merging into LMDB= ? > This fix is still working great (improved performance) on our systems. > Thanks, > Kris > > On Mon, Jun 17, 2019 at 1:04 PM Kris Zyp <kriszyp(a)gmail.com> wrote: > >> Is this still being considered/reviewed? Let me know if there are any >> other changes you would like me to make. This patch has continued to yie= ld >> significant and reliable performance improvements for us, and seems like= it >> would be nice for this to be available for other Windows users. >> >> On Fri, May 3, 2019 at 3:52 PM Kris Zyp <kriszyp(a)gmail.com> wrote: >> >>> For the sake of putting this in the email thread (other code discussion >>> in GitHub), here is the latest squashed commit of the proposed patch (w= ith >>> the on-demand, retained overlapped array to reduce re-malloc and openin= g >>> event handles): >>> https://github.com/kriszyp/node-lmdb/commit/726a9156662c703bf3d453aab75= ee222072b990f >>> >>> >>> >>> Thanks, >>> Kris >>> >>> >>> >>> *From: *Kris Zyp <kriszyp(a)gmail.com> >>> *Sent: *April 30, 2019 12:43 PM >>> *To: *Howard Chu <hyc(a)symas.com>; openldap-its(a)OpenLDAP.org >>> *Subject: *RE: (ITS#9017) Improving performance of commit sync in >>> Windows >>> >>> >>> >>> > What is the point of using writemap mode if you still need to use >>> WriteFile >>> >>> > on every individual page? >>> >>> >>> >>> As I understood from the documentation, and have observed, using >>> writemap mode is faster (and uses less temporary memory) because it doe= sn=E2=80=99t >>> require mallocs to allocate pages (docs: =E2=80=9CThis is faster and us= es fewer >>> mallocs=E2=80=9D). To be clear though, LMDB is so incredibly fast and e= fficient, >>> that in sync-mode, it takes enormous transactions before the time spent >>> allocating and creating the dirty pages with the updated b-tree is anyw= here >>> even remotely close to the time it takes to wait for disk flushing, eve= n >>> with an SSD. But the more pertinent question is efficiency, and measuri= ng >>> CPU cycles rather than time spent (efficiency is more important than ju= st >>> time spent). When I ran my tests this morning of 100 (sync) transaction= s >>> with 100 puts per transaction, times varied quite a bit, but it seemed = like >>> running with writemap enabled typically averages about 500ms of CPU and >>> with writemap disabled it typically averages around 600ms. Not a huge >>> difference, but still definitely worthwhile, I think. >>> >>> >>> >>> Caveat emptor: Measuring LMDB performance with sync interactions on >>> Windows is one of the most frustratingly erratic things to measure. It = is >>> sunny outside right now, times could be different when it starts rainin= g >>> later, but, this is what I saw this morning... >>> >>> >>> >>> > What is the performance difference between your patch using writemap, >>> and just >>> >>> > not using writemap in the first place? >>> >>> >>> >>> Running 1000 sync transactions on 3GB db with a single put per >>> transaction, without writemap map, without the patch took about 60 seco= nds. >>> And it took about 1 second with the patch with writemap mode enabled! >>> (there is no significant difference in sync times with writemap enabled= or >>> disabled with the patch.) So the difference was huge in my test. And no= t >>> only that, without the patch, the CPU usage was actually _*higher*_ >>> during that 60 seconds (close to 100% of a core) than during the execut= ion >>> with the patch for one second (close to 50%). Anyway, there are certai= nly >>> tests I have run where the differences are not as large (doing small >>> commits on large dbs accentuates the differences), but the patch always >>> seems to win. It could also be that my particular configuration causes >>> bigger differences (on an SSD drive, and maybe a more fragmented file?)= . >>> >>> >>> >>> Anyway, I added error handling for the malloc, and fixed/changed the >>> other things you suggested. Be happy to make any other changes you want= . >>> The updated patch is here: >>> >>> >>> https://github.com/kriszyp/node-lmdb/commit/25366dea9453749cf6637f43ec1= 7b9b62094acde >>> >>> >>> >>> > OVERLAPPED* ov =3D malloc((pagecount - keep) * sizeof(OVERLAPPED)); >>> >>> > Probably this ought to just be pre-allocated based on the maximum >>> number of dirty pages a txn allows. >>> >>> >>> >>> I wasn=E2=80=99t sure I understood this comment. Are you suggesting we = malloc(MDB_IDL_UM_MAX >>> * sizeof(OVERLAPPED)) for each environment, and retain it for the life = of >>> the environment? I think that is 4MB, if my math is right, which seems = like >>> a lot of memory to keep allocated (we usually have a lot of open >>> environments). If the goal is to reduce the number of mallocs, how abou= t we >>> retain the OVERLAPPED array, and only free and re-malloc if the previou= s >>> allocation wasn=E2=80=99t large enough? Then there isn=E2=80=99t unnece= ssary allocation, >>> and we only malloc when there is a bigger transaction than any previous= . I >>> put this together in a separate commit, as I wasn=E2=80=99t sure if thi= s what you >>> wanted (can squash if you prefer): >>> https://github.com/kriszyp/node-lmdb/commit/2fe68fb5269c843e2e789746a17= a4b2adefaac40 >>> >>> >>> >>> Thank you for the review! >>> >>> >>> >>> Thanks, >>> Kris >>> >>> >>> >>> *From: *Howard Chu <hyc(a)symas.com> >>> *Sent: *April 30, 2019 7:12 AM >>> *To: *kriszyp(a)gmail.com; openldap-its(a)OpenLDAP.org >>> *Subject: *Re: (ITS#9017) Improving performance of commit sync in >>> Windows >>> >>> >>> >>> kriszyp(a)gmail.com wrote: >>> >>> > Full_Name: Kristopher William Zyp >>> >>> > Version: LMDB 0.9.23 >>> >>> > OS: Windows >>> >>> > URL: >>> https://github.com/kriszyp/node-lmdb/commit/7ff525ae57684a163d32af74a0a= b9332b7fc4ce9 >>> >>> > Submission from: (NULL) (71.199.6.148) >>> >>> > >>> >>> > >>> >>> > We have seen very poor performance on the sync of commits on large >>> databases in >>> >>> > Windows. On databases with 2GB of data, in writemap mode, the sync of >>> even small >>> >>> > commits is consistently well over 100ms (without writemap it is >>> faster, but >>> >>> > still slow). It is expected that a sync should take some time while >>> waiting for >>> >>> > disk confirmation of the writes, but more concerning is that these sy= nc >>> >>> > operations (in writemap mode) are instead dominated by nearly 100% >>> system CPU >>> >>> > utilization, so operations that requires sub-millisecond b-tree updat= e >>> >>> > operations are then dominated by very large amounts of system CPU >>> cycles during >>> >>> > the sync phase. >>> >>> > >>> >>> > I think that the fundamental problem is that FlushViewOfFile seems to >>> be an O(n) >>> >>> > operation where n is the size of the file (or map). I presume that >>> Windows is >>> >>> > scanning the entire map/file for dirty pages to flush, I'm guessing >>> because it >>> >>> > doesn't have an internal index of all the dirty pages for every >>> file/map-view in >>> >>> > the OS disk cache. Therefore, the turns into an extremely expensive, >>> CPU-bound >>> >>> > operation to find the dirty pages for (large file) and initiate their >>> writes, >>> >>> > which, of course, is contrary to the whole goal of a scalable databas= e >>> system. >>> >>> > And FlushFileBuffers is also relatively slow as well. We have >>> attempted to batch >>> >>> > as many operations into single transaction as possible, but this is >>> still a very >>> >>> > large overhead. >>> >>> > >>> >>> > The Windows docs for FlushFileBuffers itself warns about the >>> inefficiencies of >>> >>> > this function ( >>> https://docs.microsoft.com/en-us/windows/desktop/api/fileapi/nf-fileapi= -flushfilebuffers >>> ). >>> >>> > Which also points to the solution: it is much faster to write out the >>> dirty >>> >>> > pages with WriteFile through a sync file handle >>> (FILE_FLAG_WRITE_THROUGH). >>> >>> > >>> >>> > The associated patch >>> >>> > ( >>> https://github.com/kriszyp/node-lmdb/commit/7ff525ae57684a163d32af74a0a= b9332b7fc4ce9 >>> ) >>> >>> > is my attempt at implementing this solution, for Windows. Fortunately= , >>> with the >>> >>> > design of LMDB, this is relatively straightforward. LMDB already >>> supports >>> >>> > writing out dirty pages with WriteFile calls. I added a write-through >>> handle for >>> >>> > sending these writes directly to disk. I then made that file-handle >>> >>> > overlapped/asynchronously, so all the writes for a commit could be >>> started in >>> >>> > overlap mode, and (at least theoretically) transfer in parallel to th= e >>> drive and >>> >>> > then used GetOverlappedResult to wait for the completion. So basicall= y >>> >>> > mdb_page_flush becomes the sync. I extended the writing of dirty page= s >>> through >>> >>> > WriteFile to writemap mode as well (for writing meta too), so that >>> WriteFile >>> >>> > with write-through can be used to flush the data without ever needing >>> to call >>> >>> > FlushViewOfFile or FlushFileBuffers. I also implemented support for >>> write >>> >>> > gathering in writemap mode where contiguous file positions infers >>> contiguous >>> >>> > memory (by tracking the starting position with wdp and writing >>> contiguous pages >>> >>> > in single operations). Sorting of the dirty list is maintained even i= n >>> writemap >>> >>> > mode for this purpose. >>> >>> >>> >>> What is the point of using writemap mode if you still need to use >>> WriteFile >>> >>> on every individual page? >>> >>> >>> >>> > The performance benefits of this patch, in my testing, are >>> considerable. Writing >>> >>> > out/syncing transactions is typically over 5x faster in writemap mode= , >>> and 2x >>> >>> > faster in standard mode. And perhaps more importantly (especially in >>> environment >>> >>> > with many threads/processes), the efficiency benefits are even larger= , >>> >>> > particularly in writemap mode, where there can be a 50-100x reduction >>> in the >>> >>> > system CPU usage by using this patch. This brings windows performance >>> with >>> >>> > sync'ed transactions in LMDB back into the range of "lightning" >>> performance :). >>> >>> >>> >>> What is the performance difference between your patch using writemap, >>> and just >>> >>> not using writemap in the first place? >>> >>> >>> >>> -- >>> >>> -- Howard Chu >>> >>> CTO, Symas Corp. http://www.symas.com >>> >>> Director, Highland Sun http://highlandsun.com/hyc/ >>> >>> Chief Architect, OpenLDAP http://www.openldap.org/project/ >>> >>> >>> >>> >>> >> --000000000000bdb86d059deaf350 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Sorry to keep pestering, but just pinging about this patch= again, as I still think this fix could benefit windows users. And at this = point, I think I can say we have tested it pretty well, running on our serv= ers for almost a year :).<div>Thanks,</div><div>Kris</div></div> <div cl= ass=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Sep 18, 2= 019 at 12:56 PM Kris Zyp <<a href=3D"mailto:kriszyp@gmail.com">kriszyp@g= mail.com</a>> wrote: </div><blockquote class=3D"gmail_quote" style=3D= "margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le= ft:1ex"><div dir=3D"ltr">Checking on this again, is this still a possibilit= y for merging into LMDB? This fix is still working great (improved performa= nce) on our systems.<div>Thanks,</div><div>Kris</div></div> <div class= =3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jun 17, 2019= at 1:04 PM Kris Zyp <<a href=3D"mailto:kriszyp@gmail.com" target=3D"_bl= ank">kriszyp(a)gmail.com</a>> wrote: </div><blockquote class=3D"gmail_q= uote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,2= 04);padding-left:1ex"><div dir=3D"ltr">Is this still being considered/revie= wed? Let me know if there are any other changes you would like me to make. = This patch has continued to yield significant and reliable performance impr= ovements for us, and seems like it would be nice for this to be available f= or other Windows users.</div> <div class=3D"gmail_quote"><div dir=3D"ltr= " class=3D"gmail_attr">On Fri, May 3, 2019 at 3:52 PM Kris Zyp <<a href= =3D"mailto:kriszyp@gmail.com" target=3D"_blank">kriszyp(a)gmail.com</a>> w= rote: </div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p= x 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div lang= =3D"EN-CA"><div>For the sake of putting this in the = email thread (other code discussion in GitHub), here is the latest squashed= commit of the proposed patch (with the on-demand, retained overlapped arra= y to reduce re-malloc and opening event handles): <a href=3D"https://github= .com/kriszyp/node-lmdb/commit/726a9156662c703bf3d453aab75ee222072b990f" tar= get=3D"_blank">https://github.com/kriszyp/node-lmdb/commit/726a9156662c703b= f3d453aab75ee222072b990f</a>=C2=A0= Thanks, Kris</u= >=C2=A0<div style=3D"border-right:none;border-bottom:none;border= -left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0cm 0cm">From: <a href=3D= "mailto:kriszyp@gmail.com" target=3D"_blank">Kris Zyp</a> Sent: A= pril 30, 2019 12:43 PM To: <a href=3D"mailto:hyc@symas.com" targe= t=3D"_blank">Howard Chu</a>; <a href=3D"mailto:openldap-its@OpenLDAP.org" t= arget=3D"_blank">openldap-its(a)OpenLDAP.org</a> Subject: RE: (ITS#= 9017) Improving performance of commit sync in Windows</div>=C2=A0> What is the = point of using writemap mode if you still need to use WriteFile</= u>> on every individual page?</= p>=C2=A0As = I understood from the documentation, and have observed, using writemap mode= is faster (and uses less temporary memory) because it doesn=E2=80=99t requ= ire mallocs to allocate pages (docs: =E2=80=9CThis is faster and uses fewer= mallocs=E2=80=9D). To be clear though, LMDB is so incredibly fast and effi= cient, that in sync-mode, it takes enormous transactions before the time sp= ent allocating and creating the dirty pages with the updated b-tree is anyw= here even remotely close to the time it takes to wait for disk flushing, ev= en with an SSD. But the more pertinent question is efficiency, and measurin= g CPU cycles rather than time spent (efficiency is more important than just= time spent). When I ran my tests this morning of 100 (sync) transactions w= ith 100 puts per transaction, times varied quite a bit, but it seemed like = running with writemap enabled typically averages about 500ms of CPU and wit= h writemap disabled it typically averages around 600ms. Not a huge differen= ce, but still definitely worthwhile, I think.=C2=A0Caveat emptor: Me= asuring LMDB performance with sync interactions on Windows is one of the mo= st frustratingly erratic things to measure. It is sunny outside right now, = times could be different when it starts raining later, but, this is what I = saw this morning...=C2=A0<u= >> What is the performance difference bet= ween your patch using writemap, and just> not using writemap in the first place?=C2=A0Running 1000 = sync transactions on 3GB db with a single put per transaction, without writ= emap map, without the patch took about 60 seconds. And it took about 1 seco= nd with the patch with writemap mode enabled! (there is no significant diff= erence in sync times with writemap enabled or disabled with the patch.) So = the difference was huge in my test. And not only that, without the patch, t= he CPU usage was actually _higher_ during that 60 seconds (close to = 100% of a core) than during the execution with the patch for one second (cl= ose to 50%).=C2=A0 Anyway, there are certainly tests I have run where the d= ifferences are not as large (doing small commits on large dbs accentuates t= he differences), but the patch always seems to win. It could also be that m= y particular configuration causes bigger differences (on an SSD drive, and = maybe a more fragmented file?).= =C2=A0Anyway, I added error handling = for the malloc, and fixed/changed the other things you suggested. Be happy = to make any other changes you want. The updated patch is here:</u= ><a href=3D"https://github.com/kriszyp/node-lmdb= /commit/25366dea9453749cf6637f43ec17b9b62094acde" target=3D"_blank">https:/= /github.com/kriszyp/node-lmdb/commit/25366dea9453749cf6637f43ec17b9b62094ac= de</a>=C2=A0> OVERLAPPED* ov =3D malloc<= /span>((pagecount - keep) * sizeof<s= pan style=3D"font-size:9pt;font-family:Consolas;color:rgb(36,41,46)">(OVERL= APPED));> Probably th= is ought to just be pre-allocated based on the maximum number of dirty page= s a txn allows.=C2=A0<= /span>I w= asn=E2=80=99t sure I understood this comment. Are you suggesting we = malloc(MDB_IDL_UM_MAX * sizeof(OVERLAPPED)) for each environment, and retai= n it for the life of the environment? I think that is 4MB, if my math is ri= ght, which seems like a lot of memory to keep allocated (we usually have a = lot of open environments). If the goal is to reduce the number of mallocs, = how about we retain the OVERLAPPED array, and only free and re-malloc if th= e previous allocation wasn=E2=80=99t large enough? Then there isn=E2=80=99t= unnecessary allocation, and we only malloc when there is a bigger transact= ion than any previous. I put this together in a separate commit, as I wasn= =E2=80=99t sure if this what you wanted (can squash if you prefer): <a href= =3D"https://github.com/kriszyp/node-lmdb/commit/2fe68fb5269c843e2e789746a17= a4b2adefaac40" target=3D"_blank">https://github.com/kriszyp/node-lmdb/commi= t/2fe68fb5269c843e2e789746a17a4b2adefaac40</a>=C2=A0Thank you for th= e review! <= p class=3D"MsoNormal">=C2=A0Thanks= , Kris=C2=A0<= div style=3D"border-right:none;border-bottom:none;border-left:none;border-t= op:1pt solid rgb(225,225,225);padding:3pt 0cm 0cm"><= b>From: <a href=3D"mailto:hyc@symas.com" target=3D"_blank">Howard Chu</= a> Sent: April 30, 2019 7:12 AM To: <a href=3D"mailto:k= riszyp(a)gmail.com" target=3D"_blank">kriszyp(a)gmail.com</a>; <a href=3D"mailt= o:openldap-its@OpenLDAP.org" target=3D"_blank">openldap-its(a)OpenLDAP.org</a= > Subject: Re: (ITS#9017) Improving performance of commit sync in= Windows</div>=C2=A0= <a href=3D"mailto:kriszyp@gmail.com" target=3D"_= blank">kriszyp(a)gmail.com</a> wrote:> Full_Name: Kristopher William Zyp> Version: LMDB 0.9.23>= OS: Windows> URL: <a href=3D"h= ttps://github.com/kriszyp/node-lmdb/commit/7ff525ae57684a163d32af74a0ab9332= b7fc4ce9" target=3D"_blank">https://github.com/kriszyp/node-lmdb/commit/7ff= 525ae57684a163d32af74a0ab9332b7fc4ce9</a>> Submission from: (NULL) (71.199.6.148)> > <= u>> We have seen very poor performance on= the sync of commits on large databases in> Windows. On databases with 2GB of data, in writemap mode, the = sync of even small> commits is = consistently well over 100ms (without writemap it is faster, but<= /u>> still slow). It is expected that a sync = should take some time while waiting for> disk confirmation of the writes, but more concerning is that thes= e sync> operations (in writemap= mode) are instead dominated by nearly 100% system CPU> utilization, so operations that requires sub-milli= second b-tree update> operation= s are then dominated by very large amounts of system CPU cycles during</= u>> the sync phase.<= p class=3D"MsoNormal">> > I = think that the fundamental problem is that FlushViewOfFile seems to be an O= (n)> operation where n is the s= ize of the file (or map). I presume that Windows is> scanning the entire map/file for dirty pages to flush= , I'm guessing because it> = doesn't have an internal index of all the dirty pages for every file/ma= p-view in> the OS disk cache. T= herefore, the turns into an extremely expensive, CPU-bound</p= >> operation to find the dirty pages for (large f= ile) and initiate their writes,&gt= ; which, of course, is contrary to the whole goal of a scalable database sy= stem.> And FlushFileBuffers is = also relatively slow as well. We have attempted to batch<= p class=3D"MsoNormal">> as many operations into single transaction as po= ssible, but this is still a very&g= t; large overhead.> <= /u>> The Windows docs for FlushFileBuffers it= self warns about the inefficiencies of> this function (<a href=3D"https://docs.microsoft.com/en-us/windows= /desktop/api/fileapi/nf-fileapi-flushfilebuffers" target=3D"_blank">https:/= /docs.microsoft.com/en-us/windows/desktop/api/fileapi/nf-fileapi-flushfileb= uffers</a>).> Which also points= to the solution: it is much faster to write out the dirty</p= >> pages with WriteFile through a sync file handl= e (FILE_FLAG_WRITE_THROUGH).> <= u>> The associated patch= > (<a href=3D"https://github.com/kriszyp/= node-lmdb/commit/7ff525ae57684a163d32af74a0ab9332b7fc4ce9" target=3D"_blank= ">https://github.com/kriszyp/node-lmdb/commit/7ff525ae57684a163d32af74a0ab9= 332b7fc4ce9</a>)> is my attempt= at implementing this solution, for Windows. Fortunately, with the<u= >> design of LMDB, this is relatively str= aightforward. LMDB already supports> writing out dirty pages with WriteFile calls. I added a write-through= handle for> sending these writ= es directly to disk. I then made that file-handle> overlapped/asynchronously, so all the writes for a comm= it could be started in> overlap= mode, and (at least theoretically) transfer in parallel to the drive and<u= >> then used GetOverlappedResult t= o wait for the completion. So basically> mdb_page_flush becomes the sync. I extended the writing of dirty = pages through> WriteFile to wri= temap mode as well (for writing meta too), so that WriteFile<= /p>> with write-through can be used to flush the = data without ever needing to call&= gt; FlushViewOfFile or FlushFileBuffers. I also implemented support for wri= te> gathering in writemap mode = where contiguous file positions infers contiguous> memory (by tracking the starting position with wdp and = writing contiguous pages> in si= ngle operations). Sorting of the dirty list is maintained even in writemap<= u>> mode for this purpose.<= u>=C2=A0What is the point of using writemap mode if you still need to use Writ= eFileon every individual page?<= /u>=C2=A0> The performance benefits of this patch, in my testing, are co= nsiderable. Writing> out/syncin= g transactions is typically over 5x faster in writemap mode, and 2x<= u>> faster in standard mode. And perhaps = more importantly (especially in environment> with many threads/processes), the efficiency benefits are eve= n larger,> particularly in writ= emap mode, where there can be a 50-100x reduction in the<= p class=3D"MsoNormal">> system CPU usage by using this patch. This bring= s windows performance with> syn= c'ed transactions in LMDB back into the range of "lightning" = performance :).=C2=A0</u= >What is the performance difference between your= patch using writemap, and justnot= using writemap in the first place?=C2=A0-- =C2=A0=C2=A0-- Howard Chu=C2=A0 CTO, Symas Corp.=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0 <a href=3D"http://www.symas.com" target=3D"_blank">http:= //www.symas.com</a>=C2=A0 Director= , Highland Sun=C2=A0=C2=A0=C2=A0=C2=A0 <a href=3D"http://highlandsun.com/hy= c/" target=3D"_blank">http://highlandsun.com/hyc/</a>=C2=A0 Chief Architect, OpenLDAP=C2=A0 <a href=3D"http:/= /www.openldap.org/project/" target=3D"_blank">http://www.openldap.org/proje= ct/</a>=C2=A0=C2=A0</div></div></blockquote></div> </blockquote></div> </blockquote></div> --000000000000bdb86d059deaf350--

1 0

(ITS#9163) warning: logical not is only applied to the left hand side of bitwise operator
by noloader＠gmail.com 06 Feb '20

06 Feb '20

Full_Name: Jeffrey Walton Version: 2.4.47 OS: OS X 10.10 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (100.18.0.145) Hi Everyone. I'm building OpenSLAP 2.4.47 from the release tarball on OS X. Clang is triggering a warning that may be of interest: gcc -g2 -O2 -march=native -fPIC -pthread -I../../include -I/usr/local/include -DNDEBUG -c -o common.o common.c ... common.c:2329:10: warning: logical not is only applied to the left hand side of this bitwise operator [-Wlogical-not-parentheses] if ( !tool_ctrl_response[j].mask & tool_type ) { ^ ~ common.c:2329:10: note: add parentheses after the '!' to evaluate the bitwise operator first if ( !tool_ctrl_response[j].mask & tool_type ) { ^ ( ) common.c:2329:10: note: add parentheses around left hand side expression to silence this warning if ( !tool_ctrl_response[j].mask & tool_type ) { ^ ( ) As written the statement is being evaluated as: (!tool_ctrl_response[j].mask) & tool_type It looks like this is what was intended: !(tool_ctrl_response[j].mask & tool_type) Perhaps the project can add parenthesis to clear the warning.

1 0

Re: (ITS#8988) Undefined Behavior in slapadd
by openldap-technical＠kolttonen.fi 03 Feb '20

03 Feb '20

This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---1463811718-1330329680-1580755187=:215607 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 8BIT Hello, On Mon, 3 Feb 2020, hyc(a)symas.com wrote: > No. The POSIX spec is *not* a part of the C spec - yet it is still valid. POSIX spec *is* a C standard that exists in addition to the ISO C standard. ISO C defines the so-called "basic language and features" of C if you can call it that. > Which simply proves the point that just because something is not defined > in the C spec does not make it invalid. The compiler guys are idiots for > taking this position. Like Jeff already said, wrongly aligned object access *is* defined by the ISO C specification. It is wrong and explicitly defined as Undefined Behaviour. Invoking UB is playing with fire, and calling compiler writers with offending names does not change that fact at all. Spending long time on comp.lang.c should be mandatory for all C programmers out there. It is shocking to invoke UB and not bother to fix it, instead blaming compiler writers and C standard writers. Best regards, Jokke Hämäläinen ---1463811718-1330329680-1580755187=:215607--

1 0

Re: (ITS#9162) dbMaxSize property does not as expected
by quanah＠symas.com 03 Feb '20

03 Feb '20

--On Monday, February 3, 2020 9:49 AM +0000 pasumarthivijaykumar(a)gmail.com wrote: > Full_Name: Vijay Kumar > Version: 2.4.48 > OS: windows > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (103.204.96.6) Please stop filing ITSes, as you clearly are working with an already broken database. This ITS will be closed. --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

Re: (ITS#8988) Undefined Behavior in slapadd
by hyc＠symas.com 03 Feb '20

03 Feb '20

openldap-technical(a)kolttonen.fi wrote: > This message is in MIME format. The first part should be readable text, > while the remaining parts are likely unreadable without MIME-aware tools. > > ---1463811718-806940296-1580670508=:196090 > Content-Type: text/plain; charset=ISO-8859-15 > Content-Transfer-Encoding: 8BIT > > > Hello, > > On Sat, 8 Jun 2019, hyc(a)symas.com wrote: > >> The gcc/clang folks have their heads up their asses. They've >> deliberately misinterpreted the spec claiming undefined behaviors are >> forbidden, supposedly to enable essential optimizations. Most of which >> only apply to obscure corner cases in compiler benchmark suites, that >> nobody in the real world ever benefits from. > > I realize this thread is very old, but Jeff and the C compiler folks are > right. All C programs that invoke undefined behavior are illegal C > programs and should be fixed. > > Posix threads are well-defined by Posix standards, so calling them > "undefined behaviour" is not a valid argument. No. The POSIX spec is *not* a part of the C spec - yet it is still valid. Which simply proves the point that just because something is not defined in the C spec does not make it invalid. The compiler guys are idiots for taking this position. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

(ITS#9162) dbMaxSize property does not as expected
by pasumarthivijaykumar＠gmail.com 03 Feb '20

03 Feb '20

Full_Name: Vijay Kumar Version: 2.4.48 OS: windows URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (103.204.96.6) if i try to set the value from property, i dont understand from where the value 1406945XXXXXX and getting set. Please check the details mentioned. 1) olcDbMaxSize: 10485760 >mdb_stat.exe -rne "C:\testMaxSize2\mdb\data.mdb" Environment Info Map address: 0000000000000000 Map size: 140694549168128 Page size: 4096 Max pages: 34349255168 Number of pages used: 2 Last transaction ID: 0 Max readers: 126 Number of readers used: 0 Reader Table Status (no active readers) >slapd.exe -T add -F ..\slapd.d -l backupContent.ldif 5e37a371 mdb_db_open: database "o=abc.net" cannot be opened: ⁿ (87). Restore from backup! 5e37a371 backend_startup_one (type=mdb, suffix="o=abc.net"): bi_db_open failed! (87) slap_startup failed 2) olcDbMaxSize: 1048576 >slapd.exe -T add -F ..\slapd.d -l backupContent.ldif 5e37a5ef mdb_db_open: database "o=abc.net" cannot be opened: ⁿ (87). Restore from backup! 5e37a5ef backend_startup_one (type=mdb, suffix="o=abc.net"): bi_db_open failed! (87) slap_startup failed >mdb_stat.exe -rne "C:\testMaxSize2\mdb\data.mdb" Environment Info Map address: 0000000000000000 Map size: 140694539730944 Page size: 4096 Max pages: 34349252864 Number of pages used: 2 Last transaction ID: 0 Max readers: 126 Number of readers used: 0 Reader Table Status (no active readers) 3) olcDbMaxSize: 1024 >slapd.exe -T add -F ..\slapd.d -l backupContent.ldif 5e37a7fd mdb_db_open: database "o=abc.net" cannot be opened: ⁿ (87). Restore from backup! 5e37a7fd backend_startup_one (type=mdb, suffix="o=abc.net"): bi_db_open failed! (87) slap_startup failed >mdb_stat.exe -rne "C:\testMaxSize2\mdb\data.mdb" Environment Info Map address: 0000000000000000 Map size: 140694538683392 Page size: 4096 Max pages: 34349252608 Number of pages used: 2 Last transaction ID: 0 Max readers: 126 Number of readers used: 0 Reader Table Status (no active readers) 5) olcDbMaxSize 10 >slapd.exe -T add -F ..\slapd.d -l backupContent.ldif 5e37a92b mdb_db_open: database "o=abc.net" cannot be opened: ⁿ (87). Restore from backup! 5e37a92b backend_startup_one (type=mdb, suffix="o=abc.net"): bi_db_open failed! (87) slap_startup failed >mdb_stat.exe -rne "C:\testMaxSize2\mdb\data.mdb" Environment Info Map address: 0000000000000000 Map size: 140694538682378 Page size: 4096 Max pages: 34349252608 Number of pages used: 2 Last transaction ID: 0 Max readers: 126 Number of readers used: 0 Reader Table Status (no active readers) 6) olcDbMaxSize 1 >slapd.exe -T add -F ..\slapd.d -l backupContent.ldif 5e37a92b mdb_db_open: database "o=abc.net" cannot be opened: ⁿ (87). Restore from backup! 5e37a92b backend_startup_one (type=mdb, suffix="o=abc.net"): bi_db_open failed! (87) slap_startup failed >mdb_stat.exe -rne "C:\testMaxSize2\mdb\data.mdb" Environment Info Map address: 0000000000000000 Map size: 140694538682369 Page size: 4096 Max pages: 34349252608 Number of pages used: 2 Last transaction ID: 0 Max readers: 126 Number of readers used: 0 Reader Table Status (no active readers) 7) olcDbMaxSize not set >mdb_stat.exe -rne "C:\testMaxSize2\mdb\data.mdb" Environment Info Map address: 0000000000000000 Map size: 1048576 Page size: 4096 Max pages: 256 Number of pages used: 254 Last transaction ID: 104 Max readers: 126 Number of readers used: 0 Reader Table Status (no active readers)

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs