Return-Path: X-Original-To: apmail-uima-user-archive@www.apache.org Delivered-To: apmail-uima-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 587AE17864 for ; Mon, 13 Apr 2015 16:21:20 +0000 (UTC) Received: (qmail 53783 invoked by uid 500); 13 Apr 2015 16:21:20 -0000 Delivered-To: apmail-uima-user-archive@uima.apache.org Received: (qmail 53733 invoked by uid 500); 13 Apr 2015 16:21:20 -0000 Mailing-List: contact user-help@uima.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@uima.apache.org Delivered-To: mailing list user@uima.apache.org Received: (qmail 53717 invoked by uid 99); 13 Apr 2015 16:21:19 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Apr 2015 16:21:19 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of uimaee@gmail.com designates 209.85.212.181 as permitted sender) Received: from [209.85.212.181] (HELO mail-wi0-f181.google.com) (209.85.212.181) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Apr 2015 16:20:53 +0000 Received: by wiax7 with SMTP id x7so68690046wia.0 for ; Mon, 13 Apr 2015 09:19:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=eVbSGKCqDXu1DFLYQh9s9UWsatPPcLG3H0dnKwAXcJQ=; b=lb80T2E7mQMgpQYIZbI8UvFjlVLGZLMI5+Lhi7zpQ+3zyJsHZy8Axb2BiKkl/XPgXJ X8vlBMEJ1Qp9rMm+4BS6jB/CWiFJQQ7qeE+M+wJTn0l6eRJ6UqrCE6kII7Iom+Zed1zA Rykedi2l2Q3acdGvxZ0L6dRL4Wj5pnxSg+ej+lDhdFFjuoRrB1bo1va4N8EomM2Lgzug bJNJ2TXEdYJ/XmdvXBAjve7DhC/rZUgRoV9ugVkQAq58hbYnsD9n3wVuRhlF+XRfmKsS Ws2VkEDWqu/fnJe+9xEXjrAPauYjc+wvpJzhSkY2y4mfpC+mx7+l0txTuqRw8/GuZffR QejA== MIME-Version: 1.0 X-Received: by 10.180.96.41 with SMTP id dp9mr22660909wib.77.1428941962437; Mon, 13 Apr 2015 09:19:22 -0700 (PDT) Received: by 10.27.214.17 with HTTP; Mon, 13 Apr 2015 09:19:22 -0700 (PDT) In-Reply-To: References: Date: Mon, 13 Apr 2015 12:19:22 -0400 Message-ID: Subject: Re: UIMA CPE appears not to utilise more than a single thread From: Jaroslaw Cwiklik To: user@uima.apache.org Content-Type: multipart/alternative; boundary=f46d043bdc58136c9a05139d7a95 X-Virus-Checked: Checked by ClamAV on apache.org --f46d043bdc58136c9a05139d7a95 Content-Type: text/plain; charset=UTF-8 Not sure if this is the cause but check if your AE descriptor has this true Jerry On Mon, Apr 13, 2015 at 12:07 PM, Eddie Epstein wrote: > The CPE runs pipeline threads in parallel, not necessarily CAS processors. > In a CPE descriptor, generally all non-CasConsumer components make up the > pipeline. > > Change the following line to indicate how many pipeline threads to run, and > make sure the casPoolSize is number of threads +2. > > > > Eddie > > On Mon, Apr 13, 2015 at 7:44 AM, Mario Gazzo > wrote: > > > It appears that I can only utilise a single CAS processor even if I > > specify many more. I am not sure what I am doing wrong but I think I must > > be missing something important in my configuration. > > > > We only need multithreading and not the distributed features of UIMA CPE > > or similar. I copied and modified the UIMA FIT CpePipeline and CpeBuilder > > to do this and I only altered thread counts and error handling since I > want > > the CAS just to be dropped on exceptions. I have verified that the > accurate > > number of CAS processors are created using the debugger and I can in > > JConsole see that an equivalent amount of active threads are created but > > only one thread seems to be fed from my simple custom collection reader, > > which in the simple test setup only reads input entries from a file. I > can > > see this because I log the thread id inside the AEs, which is always the > > same. I have also verified that the CAS pool size equals the number of > > processors + 2. > > > > Is there some additional collection reader configuration required to feed > > all the other CAS processors? > > > > > > > > > > > > > --f46d043bdc58136c9a05139d7a95--