[jira] [Commented] (DIRSTUDIO-1174) Directory Studio startup very slow due to schema LDIF processing
[
https://issues.apache.org/jira/browse/DIRSTUDIO-1174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412851#comment-16412851
]
Aaron Burgemeister commented on DIRSTUDIO-1174:
---
I have an old version (12.0.6) of Yourkit which I just tried pointing to
Studio; I am not sure what all I should see that may help, other than the
couple dozen garbage collections as Studio starts, possibly because of
inefficient memory use related to schema parsing, or possibly just because the
tool is starting up. I have spent more time with Eclipse Memory Analyzer in the
past when doing memory stuff, but if there is anything I can specifically check
I am willing to do that.
I believe your understanding is correct in that the schema LDIFs are parsed and
something about that process takes a fair bit of time. I can probably delete
these files to recover performance, but I imagine there is a good reason for
them, like perhaps not needing to grab schema every time a connection is opened
since the cached copy can be referenced instead. Parsing schema LDIFs at
Studio startup seems like a less-great idea than parsing them at connection
creation time, since the latter situation may only need to parse one, or a few,
at a time, but I definitely do not understand all inner workings of Studio to
know the potential impact of that kind of change. On the other hand, taking a
second or two to parse the schema may also be high, so if we can find out how
to optimize that it may not be a huge deal to parse them during startup
(assuming there is significant value in doing so all at once).
> Directory Studio startup very slow due to schema LDIF processing
>
>
> Key: DIRSTUDIO-1174
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1174
> Project: Directory Studio
> Issue Type: Bug
> Components: studio-connection
>Affects Versions: 2.0.0-M13
> Environment: openSUSE Linux (installed on my laptop)
> Sun/Oracle Java 1.8.0_111 (previously 1.7 with same issue)
> Apache Directory Studio 2.0.0 M12 and M13, plus earlier milestones too
>Reporter: Aaron Burgemeister
>Priority: Major
> Labels: LDIF, schema, startup-time
>
> For the past couple years startup of Apache Directory Studio has slowed down
> to the point where it takes more than a minute on my not-a-slouch laptop to
> start. Other systems, VMs with new installs, start much faster, even on the
> same laptop, implying something other than the base product is at fault. As
> a result, I had suspected maybe Directory Studio slowed down precipitously
> due to the number of stored connections, but never confirmed the same.
> Today I connected strace to the 'java' process as it started and noticed the
> following:
>
> [pid 30108] *1521902717*.154740
> open("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core/schema-ba001fb7-4b83-4dca-be44-517c14139f4b.ldif",
> O_RDONLY) = *-1 ENOENT (No such file or directory)*
> [pid 30108] *1521902717*.154906
> stat("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core",
> \{st_mode=S_IFDIR|0755, st_size=5378, ...}) = 0
> [pid 30108] *1521902717*.154948
> open("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core/schema-95e1202e-9a67-418c-afe9-b02f4e7c06df.ldif",
> O_RDONLY) = *-1 ENOENT (No such file or directory)*
> [pid 30108] *1521902717*.155019
> stat("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core",
> \{st_mode=S_IFDIR|0755, st_size=5378, ...}) = 0
> [pid 30108] *1521902717*.155053
> open("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core/schema-687f43f6-9d05-4d08-b159-35b0e76dc95a.ldif",
> O_RDONLY) = *-1 ENOENT (No such file or directory)*
> [pid 30108] *1521902717*.155120
> stat("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core",
> \{st_mode=S_IFDIR|0755, st_size=5378, ...}) = 0
> [pid 30108] *1521902717*.155154
> open("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core/schema-d62d0e10-c81e-4477-81a2-ac2c9e5c7169.ldif",
> O_RDONLY) = *121*
> [pid 30108] *1521902718*.698702
> stat("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core",
> \{st_mode=S_IFDIR|0755, st_size=5378, ...}) = 0
> [pid 30108] *1521902718*.698800
> open("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core/schema-7b6a9a7c-2192-4b24-8874-1378e5b1b30c.ldif",
> O_RDONLY) = *126*
> [pid 30108] *1521902719*.770570
>
Re: [jira] [Created] (DIRSTUDIO-1174) Directory Studio startup very slow due to schema LDIF processing
Le 24/03/2018 à 19:30, Lothar Haeger a écrit : > Aaron Burgemeister (JIRA) wrote: > >> My Directory Studio's total startup time: sixty-one (61) seconds. >> Time spent (per strace) reading schema files: fifty-five (55) seconds. >> Estimated non-schema startup time: six (6) seconds. > > I've tried with current Studio on macOS: 40 seconds startup time with 25 > schema-* files (300-700k each) in > ~/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrow > ser.core. Renamed > ~/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrow > ser.core out of the way and startup time went down to 5 seconds. > Yep, there is clearly a problem. What I'd like to be sure is that it's caused by the LDIF parsing, and if so, we have options : - first of all, make teh svanner more efficient (will take some time) - avoid reading the schema for *each* connection at startup, it's enough to do it when needed (that would probably be an easier workaround to implement). -- Emmanuel Lecharny Symas.com directory.apache.org
Re: [jira] [Created] (DIRSTUDIO-1174) Directory Studio startup very slow due to schema LDIF processing
Aaron Burgemeister (JIRA) wrote: > My Directory Studio's total startup time: sixty-one (61) seconds. > Time spent (per strace) reading schema files: fifty-five (55) seconds. > Estimated non-schema startup time: six (6) seconds. I've tried with current Studio on macOS: 40 seconds startup time with 25 schema-* files (300-700k each) in ~/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrow ser.core. Renamed ~/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrow ser.core out of the way and startup time went down to 5 seconds.
[jira] [Comment Edited] (DIRAPI-312) Add an explaination after the log error and message numbers
[
https://issues.apache.org/jira/browse/DIRAPI-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16403361#comment-16403361
]
Emmanuel Lecharny edited comment on DIRAPI-312 at 3/24/18 5:46 PM:
---
Done projects :
* api-asn1-api
* api-asn1-ber
* api-ldap-model
** cursor
** entry
** filter
** ldif
** message
** name
* api-ldap-net-mina
* api-ldap-schema-converter
* api-ldap-schema-data
* api-util
was (Author: elecharny):
Done projects :
* api-asn1-api
* api-asn1-ber
* api-ldap-model
** cursor
** entry
** filter
** ldif
** message
* api-ldap-net-mina
* api-ldap-schema-converter
* api-ldap-schema-data
* api-util
> Add an explaination after the log error and message numbers
> ---
>
> Key: DIRAPI-312
> URL: https://issues.apache.org/jira/browse/DIRAPI-312
> Project: Directory Client API
> Issue Type: Improvement
>Affects Versions: 1.0.0
>Reporter: Emmanuel Lecharny
>Priority: Major
> Fix For: 2.0.0
>
>
> We have many error and message logs which are just numbers, like
> {{ERR_12047}}. It would be better to use such a value :
> {{ERR_12035_BAD_MODRDN_OPERATION}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DIRSTUDIO-1174) Directory Studio startup very slow due to schema LDIF processing
[
https://issues.apache.org/jira/browse/DIRSTUDIO-1174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412687#comment-16412687
]
Emmanuel Lecharny commented on DIRSTUDIO-1174:
--
Stefan, AFAIU, we will parse every schema associated with any configured
connections. With hundred of such connections, that might take a while. A I
assuming correctly that is what's going on on startup?
> Directory Studio startup very slow due to schema LDIF processing
>
>
> Key: DIRSTUDIO-1174
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1174
> Project: Directory Studio
> Issue Type: Bug
> Components: studio-connection
>Affects Versions: 2.0.0-M13
> Environment: openSUSE Linux (installed on my laptop)
> Sun/Oracle Java 1.8.0_111 (previously 1.7 with same issue)
> Apache Directory Studio 2.0.0 M12 and M13, plus earlier milestones too
>Reporter: Aaron Burgemeister
>Priority: Major
> Labels: LDIF, schema, startup-time
>
> For the past couple years startup of Apache Directory Studio has slowed down
> to the point where it takes more than a minute on my not-a-slouch laptop to
> start. Other systems, VMs with new installs, start much faster, even on the
> same laptop, implying something other than the base product is at fault. As
> a result, I had suspected maybe Directory Studio slowed down precipitously
> due to the number of stored connections, but never confirmed the same.
> Today I connected strace to the 'java' process as it started and noticed the
> following:
>
> [pid 30108] *1521902717*.154740
> open("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core/schema-ba001fb7-4b83-4dca-be44-517c14139f4b.ldif",
> O_RDONLY) = *-1 ENOENT (No such file or directory)*
> [pid 30108] *1521902717*.154906
> stat("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core",
> \{st_mode=S_IFDIR|0755, st_size=5378, ...}) = 0
> [pid 30108] *1521902717*.154948
> open("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core/schema-95e1202e-9a67-418c-afe9-b02f4e7c06df.ldif",
> O_RDONLY) = *-1 ENOENT (No such file or directory)*
> [pid 30108] *1521902717*.155019
> stat("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core",
> \{st_mode=S_IFDIR|0755, st_size=5378, ...}) = 0
> [pid 30108] *1521902717*.155053
> open("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core/schema-687f43f6-9d05-4d08-b159-35b0e76dc95a.ldif",
> O_RDONLY) = *-1 ENOENT (No such file or directory)*
> [pid 30108] *1521902717*.155120
> stat("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core",
> \{st_mode=S_IFDIR|0755, st_size=5378, ...}) = 0
> [pid 30108] *1521902717*.155154
> open("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core/schema-d62d0e10-c81e-4477-81a2-ac2c9e5c7169.ldif",
> O_RDONLY) = *121*
> [pid 30108] *1521902718*.698702
> stat("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core",
> \{st_mode=S_IFDIR|0755, st_size=5378, ...}) = 0
> [pid 30108] *1521902718*.698800
> open("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core/schema-7b6a9a7c-2192-4b24-8874-1378e5b1b30c.ldif",
> O_RDONLY) = *126*
> [pid 30108] *1521902719*.770570
> stat("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core",
> \{st_mode=S_IFDIR|0755, st_size=5378, ...}) = 0
> [pid 30108] *1521902719*.770660
> open("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core/schema-b3b02838-067f-4f24-bf92-6bf3fccdbc52.ldif",
> O_RDONLY) = *127*
> [pid 30108] *1521902721*.198417
> stat("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core",
> \{st_mode=S_IFDIR|0755, st_size=5378, ...}) = 0
>
> Notice the timestamps (bolded near beginning of line) and how they change
> based on whether or not a schema LDIF file was found (bolded near end of
> line) and, presumably, processed. When a file is not found, subsequent files
> are sought immediately without significantly delaying startup.
> These schema files are all under 1 MiB in size, but most of them are several
> hundred KiBs, approaching the 1 MiB size, so depending on what Directory
> Studio is doing as it reads and processes these files, it would seem that
> this introduces the slowness when a file is found.
> Looking for an existing issue I found DIRSTUDIO-1027 which may be related.
> During startup of Directory Studio one of my laptop's eight cores
[jira] [Commented] (DIRSTUDIO-1174) Directory Studio startup very slow due to schema LDIF processing
[
https://issues.apache.org/jira/browse/DIRSTUDIO-1174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412686#comment-16412686
]
Emmanuel Lecharny commented on DIRSTUDIO-1174:
--
Interesting findings...
Would you be able to run a profiler on Studio, like YourKit ?
> Directory Studio startup very slow due to schema LDIF processing
>
>
> Key: DIRSTUDIO-1174
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1174
> Project: Directory Studio
> Issue Type: Bug
> Components: studio-connection
>Affects Versions: 2.0.0-M13
> Environment: openSUSE Linux (installed on my laptop)
> Sun/Oracle Java 1.8.0_111 (previously 1.7 with same issue)
> Apache Directory Studio 2.0.0 M12 and M13, plus earlier milestones too
>Reporter: Aaron Burgemeister
>Priority: Major
> Labels: LDIF, schema, startup-time
>
> For the past couple years startup of Apache Directory Studio has slowed down
> to the point where it takes more than a minute on my not-a-slouch laptop to
> start. Other systems, VMs with new installs, start much faster, even on the
> same laptop, implying something other than the base product is at fault. As
> a result, I had suspected maybe Directory Studio slowed down precipitously
> due to the number of stored connections, but never confirmed the same.
> Today I connected strace to the 'java' process as it started and noticed the
> following:
>
> [pid 30108] *1521902717*.154740
> open("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core/schema-ba001fb7-4b83-4dca-be44-517c14139f4b.ldif",
> O_RDONLY) = *-1 ENOENT (No such file or directory)*
> [pid 30108] *1521902717*.154906
> stat("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core",
> \{st_mode=S_IFDIR|0755, st_size=5378, ...}) = 0
> [pid 30108] *1521902717*.154948
> open("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core/schema-95e1202e-9a67-418c-afe9-b02f4e7c06df.ldif",
> O_RDONLY) = *-1 ENOENT (No such file or directory)*
> [pid 30108] *1521902717*.155019
> stat("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core",
> \{st_mode=S_IFDIR|0755, st_size=5378, ...}) = 0
> [pid 30108] *1521902717*.155053
> open("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core/schema-687f43f6-9d05-4d08-b159-35b0e76dc95a.ldif",
> O_RDONLY) = *-1 ENOENT (No such file or directory)*
> [pid 30108] *1521902717*.155120
> stat("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core",
> \{st_mode=S_IFDIR|0755, st_size=5378, ...}) = 0
> [pid 30108] *1521902717*.155154
> open("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core/schema-d62d0e10-c81e-4477-81a2-ac2c9e5c7169.ldif",
> O_RDONLY) = *121*
> [pid 30108] *1521902718*.698702
> stat("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core",
> \{st_mode=S_IFDIR|0755, st_size=5378, ...}) = 0
> [pid 30108] *1521902718*.698800
> open("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core/schema-7b6a9a7c-2192-4b24-8874-1378e5b1b30c.ldif",
> O_RDONLY) = *126*
> [pid 30108] *1521902719*.770570
> stat("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core",
> \{st_mode=S_IFDIR|0755, st_size=5378, ...}) = 0
> [pid 30108] *1521902719*.770660
> open("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core/schema-b3b02838-067f-4f24-bf92-6bf3fccdbc52.ldif",
> O_RDONLY) = *127*
> [pid 30108] *1521902721*.198417
> stat("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core",
> \{st_mode=S_IFDIR|0755, st_size=5378, ...}) = 0
>
> Notice the timestamps (bolded near beginning of line) and how they change
> based on whether or not a schema LDIF file was found (bolded near end of
> line) and, presumably, processed. When a file is not found, subsequent files
> are sought immediately without significantly delaying startup.
> These schema files are all under 1 MiB in size, but most of them are several
> hundred KiBs, approaching the 1 MiB size, so depending on what Directory
> Studio is doing as it reads and processes these files, it would seem that
> this introduces the slowness when a file is found.
> Looking for an existing issue I found DIRSTUDIO-1027 which may be related.
> During startup of Directory Studio one of my laptop's eight cores is fully
> utilized, which makes me think this may be more about processing the LDIF
> than just swapping memory due
[jira] [Created] (DIRSTUDIO-1174) Directory Studio startup very slow due to schema LDIF processing
Aaron Burgemeister created DIRSTUDIO-1174:
-
Summary: Directory Studio startup very slow due to schema LDIF
processing
Key: DIRSTUDIO-1174
URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1174
Project: Directory Studio
Issue Type: Bug
Components: studio-connection
Affects Versions: 2.0.0-M13
Environment: openSUSE Linux (installed on my laptop)
Sun/Oracle Java 1.8.0_111 (previously 1.7 with same issue)
Apache Directory Studio 2.0.0 M12 and M13, plus earlier milestones too
Reporter: Aaron Burgemeister
For the past couple years startup of Apache Directory Studio has slowed down to
the point where it takes more than a minute on my not-a-slouch laptop to start.
Other systems, VMs with new installs, start much faster, even on the same
laptop, implying something other than the base product is at fault. As a
result, I had suspected maybe Directory Studio slowed down precipitously due to
the number of stored connections, but never confirmed the same.
Today I connected strace to the 'java' process as it started and noticed the
following:
[pid 30108] *1521902717*.154740
open("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core/schema-ba001fb7-4b83-4dca-be44-517c14139f4b.ldif",
O_RDONLY) = *-1 ENOENT (No such file or directory)*
[pid 30108] *1521902717*.154906
stat("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core",
\{st_mode=S_IFDIR|0755, st_size=5378, ...}) = 0
[pid 30108] *1521902717*.154948
open("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core/schema-95e1202e-9a67-418c-afe9-b02f4e7c06df.ldif",
O_RDONLY) = *-1 ENOENT (No such file or directory)*
[pid 30108] *1521902717*.155019
stat("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core",
\{st_mode=S_IFDIR|0755, st_size=5378, ...}) = 0
[pid 30108] *1521902717*.155053
open("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core/schema-687f43f6-9d05-4d08-b159-35b0e76dc95a.ldif",
O_RDONLY) = *-1 ENOENT (No such file or directory)*
[pid 30108] *1521902717*.155120
stat("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core",
\{st_mode=S_IFDIR|0755, st_size=5378, ...}) = 0
[pid 30108] *1521902717*.155154
open("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core/schema-d62d0e10-c81e-4477-81a2-ac2c9e5c7169.ldif",
O_RDONLY) = *121*
[pid 30108] *1521902718*.698702
stat("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core",
\{st_mode=S_IFDIR|0755, st_size=5378, ...}) = 0
[pid 30108] *1521902718*.698800
open("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core/schema-7b6a9a7c-2192-4b24-8874-1378e5b1b30c.ldif",
O_RDONLY) = *126*
[pid 30108] *1521902719*.770570
stat("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core",
\{st_mode=S_IFDIR|0755, st_size=5378, ...}) = 0
[pid 30108] *1521902719*.770660
open("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core/schema-b3b02838-067f-4f24-bf92-6bf3fccdbc52.ldif",
O_RDONLY) = *127*
[pid 30108] *1521902721*.198417
stat("/home/ab/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core",
\{st_mode=S_IFDIR|0755, st_size=5378, ...}) = 0
Notice the timestamps (bolded near beginning of line) and how they change based
on whether or not a schema LDIF file was found (bolded near end of line) and,
presumably, processed. When a file is not found, subsequent files are sought
immediately without significantly delaying startup.
These schema files are all under 1 MiB in size, but most of them are several
hundred KiBs, approaching the 1 MiB size, so depending on what Directory Studio
is doing as it reads and processes these files, it would seem that this
introduces the slowness when a file is found.
Looking for an existing issue I found DIRSTUDIO-1027 which may be related.
During startup of Directory Studio one of my laptop's eight cores is fully
utilized, which makes me think this may be more about processing the LDIF than
just swapping memory due to inefficient data structures, but I am not a memory
management expert, so I only mention the possibility here in case it helps find
the root cause quickly.
My Directory Studio's total startup time: sixty-one (61) seconds.
Time spent (per strace) reading schema files: fifty-five (55) seconds.
Estimated non-schema startup time: six (6) seconds.
Steps to duplicate:
Have a lot, e.g. 100, of stored schema LDIF files from previous connections.
Startup Apache Directory Studio.
Expected results:
[jira] [Comment Edited] (DIRAPI-312) Add an explaination after the log error and message numbers
[
https://issues.apache.org/jira/browse/DIRAPI-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16403361#comment-16403361
]
Emmanuel Lecharny edited comment on DIRAPI-312 at 3/24/18 3:09 PM:
---
Done projects :
* api-asn1-api
* api-asn1-ber
* api-ldap-model
** cursor
** entry
** filter
** ldif
** message
* api-ldap-net-mina
* api-ldap-schema-converter
* api-ldap-schema-data
* api-util
was (Author: elecharny):
Done projects :
* api-asn1-api
* api-asn1-ber
* api-ldap-model
** cursor
** entry
** filter
** ldif
* api-ldap-net-mina
* api-ldap-schema-converter
* api-ldap-schema-data
* api-util
> Add an explaination after the log error and message numbers
> ---
>
> Key: DIRAPI-312
> URL: https://issues.apache.org/jira/browse/DIRAPI-312
> Project: Directory Client API
> Issue Type: Improvement
>Affects Versions: 1.0.0
>Reporter: Emmanuel Lecharny
>Priority: Major
> Fix For: 2.0.0
>
>
> We have many error and message logs which are just numbers, like
> {{ERR_12047}}. It would be better to use such a value :
> {{ERR_12035_BAD_MODRDN_OPERATION}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
