Re: Performance degradation in UIMA3
Hi Marshall, thanks for the quick reply, I'll give it a try and get back to you. Best regards, Augusto > On 29 Jun 2020, at 16:47, Marshall Schor wrote: > > External email – Do not click links or open attachments unless you recognize > the sender and know that the content is safe. > > > Hi, > > I've made a possible fix for this in the uimaj-master (the uimaj-core project) > > It would be great if you could test this on your big system. > > Thanks. > > -Marshall > > P.S., it's quite possible this issue was the "first one", and there may be > others which will now surface (assuming this one is now fixed), for this level > of multi-threading. We would love to hear of other issues if they arise :-) > > On 6/29/2020 6:15 AM, Augusto Ribeiro Silva wrote: >> Hi all, >> >> I am writing because I noticed that our pipelines got considerably slower >> after updating to UIMA3. The cause of the slowdown seems to be the fact that >> the method getJCasRegisteredType located in TypeSystemImpl uses a >> synchronised block. We haven't noticed it before but when I was running a >> pipeline in a large machine (48 cores with 80 worker threads) many of the >> threads were blocked in this specific method. >> >> I just wanted to point that this is a big problem for us and I am not sure >> if you are aware or if there is some workaround. I am at this point >> considering packaging our own version of UIMA without the synchronised block >> since our types are not dynamic and should be loaded when the pipeline >> starts so it is unlikely that we need the synchronised access to the type >> registry. >> >> Best regards, >> Augusto >> >> >> >> Disclaimer: >> This email and any files transmitted with it are confidential and directed >> solely for the use of the intended addressee or addressees and may contain >> information that is legally privileged, confidential, and exempt from >> disclosure. If you have received this email in error, please notify the >> sender by telephone, fax, or return email and immediately delete this email >> and any files transmitted along with it. Unintended recipients are not >> authorized to disclose, disseminate, distribute, copy or take any action in >> reliance on information contained in this email and/or any files attached >> thereto, in any manner other than to notify the sender; any unauthorized use >> is subject to legal prosecution. >> >> Disclaimer: This email and any files transmitted with it are confidential and directed solely for the use of the intended addressee or addressees and may contain information that is legally privileged, confidential, and exempt from disclosure. If you have received this email in error, please notify the sender by telephone, fax, or return email and immediately delete this email and any files transmitted along with it. Unintended recipients are not authorized to disclose, disseminate, distribute, copy or take any action in reliance on information contained in this email and/or any files attached thereto, in any manner other than to notify the sender; any unauthorized use is subject to legal prosecution.
Re: Performance degradation in UIMA3
Hi, I've made a possible fix for this in the uimaj-master (the uimaj-core project) It would be great if you could test this on your big system. Thanks. -Marshall P.S., it's quite possible this issue was the "first one", and there may be others which will now surface (assuming this one is now fixed), for this level of multi-threading. We would love to hear of other issues if they arise :-) On 6/29/2020 6:15 AM, Augusto Ribeiro Silva wrote: > Hi all, > > I am writing because I noticed that our pipelines got considerably slower > after updating to UIMA3. The cause of the slowdown seems to be the fact that > the method getJCasRegisteredType located in TypeSystemImpl uses a > synchronised block. We haven't noticed it before but when I was running a > pipeline in a large machine (48 cores with 80 worker threads) many of the > threads were blocked in this specific method. > > I just wanted to point that this is a big problem for us and I am not sure if > you are aware or if there is some workaround. I am at this point considering > packaging our own version of UIMA without the synchronised block since our > types are not dynamic and should be loaded when the pipeline starts so it is > unlikely that we need the synchronised access to the type registry. > > Best regards, > Augusto > > > > Disclaimer: > This email and any files transmitted with it are confidential and directed > solely for the use of the intended addressee or addressees and may contain > information that is legally privileged, confidential, and exempt from > disclosure. If you have received this email in error, please notify the > sender by telephone, fax, or return email and immediately delete this email > and any files transmitted along with it. Unintended recipients are not > authorized to disclose, disseminate, distribute, copy or take any action in > reliance on information contained in this email and/or any files attached > thereto, in any manner other than to notify the sender; any unauthorized use > is subject to legal prosecution. > >
Re: Announcing ApacheCon @Home 2020
unusbscribe On Mon, Jun 29, 2020 at 6:56 AM Rich Bowen wrote: > Hi, Apache enthusiast! > > (You’re receiving this because you’re subscribed to one or more dev or > user mailing lists for an Apache Software Foundation project.) > > The ApacheCon Planners and the Apache Software Foundation are pleased to > announce that ApacheCon @Home will be held online, September 29th > through October 1st, 2020. We’ll be featuring content from dozens of our > projects, as well as content about community, how Apache works, business > models around Apache software, the legal aspects of open source, and > many other topics. > > Full details about the event, and registration, is available at > https://apachecon.com/acah2020 > > Due to the confusion around how and where this event was going to be > held, and in order to open up to presenters from around the world who > may previously have been unable or unwilling to travel, we’ve reopened > the Call For Presentations until July 13th. Submit your talks today at > https://acna2020.jamhosted.net/ > > We hope to see you at the event! > Rich Bowen, VP Conferences, The Apache Software Foundation >
Re: Performance degradation in UIMA3
https://issues.apache.org/jira/browse/UIMA-6249 On 6/29/2020 8:32 AM, Marshall Schor wrote: > Hi, > > Thanks for this. Investigating... -Marshall > > > On 6/29/2020 6:15 AM, Augusto Ribeiro Silva wrote: >> Hi all, >> >> I am writing because I noticed that our pipelines got considerably slower >> after updating to UIMA3. The cause of the slowdown seems to be the fact that >> the method getJCasRegisteredType located in TypeSystemImpl uses a >> synchronised block. We haven't noticed it before but when I was running a >> pipeline in a large machine (48 cores with 80 worker threads) many of the >> threads were blocked in this specific method. >> >> I just wanted to point that this is a big problem for us and I am not sure >> if you are aware or if there is some workaround. I am at this point >> considering packaging our own version of UIMA without the synchronised block >> since our types are not dynamic and should be loaded when the pipeline >> starts so it is unlikely that we need the synchronised access to the type >> registry. >> >> Best regards, >> Augusto >> >> >> >> Disclaimer: >> This email and any files transmitted with it are confidential and directed >> solely for the use of the intended addressee or addressees and may contain >> information that is legally privileged, confidential, and exempt from >> disclosure. If you have received this email in error, please notify the >> sender by telephone, fax, or return email and immediately delete this email >> and any files transmitted along with it. Unintended recipients are not >> authorized to disclose, disseminate, distribute, copy or take any action in >> reliance on information contained in this email and/or any files attached >> thereto, in any manner other than to notify the sender; any unauthorized use >> is subject to legal prosecution. >> >>
Re: Performance degradation in UIMA3
Hi, Thanks for this. Investigating... -Marshall On 6/29/2020 6:15 AM, Augusto Ribeiro Silva wrote: > Hi all, > > I am writing because I noticed that our pipelines got considerably slower > after updating to UIMA3. The cause of the slowdown seems to be the fact that > the method getJCasRegisteredType located in TypeSystemImpl uses a > synchronised block. We haven't noticed it before but when I was running a > pipeline in a large machine (48 cores with 80 worker threads) many of the > threads were blocked in this specific method. > > I just wanted to point that this is a big problem for us and I am not sure if > you are aware or if there is some workaround. I am at this point considering > packaging our own version of UIMA without the synchronised block since our > types are not dynamic and should be loaded when the pipeline starts so it is > unlikely that we need the synchronised access to the type registry. > > Best regards, > Augusto > > > > Disclaimer: > This email and any files transmitted with it are confidential and directed > solely for the use of the intended addressee or addressees and may contain > information that is legally privileged, confidential, and exempt from > disclosure. If you have received this email in error, please notify the > sender by telephone, fax, or return email and immediately delete this email > and any files transmitted along with it. Unintended recipients are not > authorized to disclose, disseminate, distribute, copy or take any action in > reliance on information contained in this email and/or any files attached > thereto, in any manner other than to notify the sender; any unauthorized use > is subject to legal prosecution. > >
Announcing ApacheCon @Home 2020
Hi, Apache enthusiast! (You’re receiving this because you’re subscribed to one or more dev or user mailing lists for an Apache Software Foundation project.) The ApacheCon Planners and the Apache Software Foundation are pleased to announce that ApacheCon @Home will be held online, September 29th through October 1st, 2020. We’ll be featuring content from dozens of our projects, as well as content about community, how Apache works, business models around Apache software, the legal aspects of open source, and many other topics. Full details about the event, and registration, is available at https://apachecon.com/acah2020 Due to the confusion around how and where this event was going to be held, and in order to open up to presenters from around the world who may previously have been unable or unwilling to travel, we’ve reopened the Call For Presentations until July 13th. Submit your talks today at https://acna2020.jamhosted.net/ We hope to see you at the event! Rich Bowen, VP Conferences, The Apache Software Foundation
Performance degradation in UIMA3
Hi all, I am writing because I noticed that our pipelines got considerably slower after updating to UIMA3. The cause of the slowdown seems to be the fact that the method getJCasRegisteredType located in TypeSystemImpl uses a synchronised block. We haven't noticed it before but when I was running a pipeline in a large machine (48 cores with 80 worker threads) many of the threads were blocked in this specific method. I just wanted to point that this is a big problem for us and I am not sure if you are aware or if there is some workaround. I am at this point considering packaging our own version of UIMA without the synchronised block since our types are not dynamic and should be loaded when the pipeline starts so it is unlikely that we need the synchronised access to the type registry. Best regards, Augusto Disclaimer: This email and any files transmitted with it are confidential and directed solely for the use of the intended addressee or addressees and may contain information that is legally privileged, confidential, and exempt from disclosure. If you have received this email in error, please notify the sender by telephone, fax, or return email and immediately delete this email and any files transmitted along with it. Unintended recipients are not authorized to disclose, disseminate, distribute, copy or take any action in reliance on information contained in this email and/or any files attached thereto, in any manner other than to notify the sender; any unauthorized use is subject to legal prosecution.
