[
https://issues.apache.org/jira/browse/SOLR-3658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13419755#comment-13419755
]
Yonik Seeley edited comment on SOLR-3658 at 7/21/12 7:41 AM:
-------------------------------------------------------------
Other thing to keep in mind memory-wise is that each thread is associated with
a number of outgoing update requests and other associated state, which in a
realistic system probably take up more mem than the thread stack.
edit: Another thing to note is that if Java thread stacks are treated the same
as C stacks (and I believe they are), then the max stack size has nothing to do
with how real RAM is used by the stack (it's expanded as needed by mapping real
RAM to the address space via the MMU). In 32 bit programs, it's still a
resource you can run out of easily of course.
was (Author: [email protected]):
Other thing to keep in mind memory-wise is that each thread is associated
with a number of outgoing update requests and other associated state, which in
a realistic system probably take up more mem than the thread stack.
> SolrCmdDistributor can briefly create spikes of threads in the thousands.
> -------------------------------------------------------------------------
>
> Key: SOLR-3658
> URL: https://issues.apache.org/jira/browse/SOLR-3658
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Reporter: Mark Miller
> Assignee: Mark Miller
> Fix For: 4.0, 5.0
>
> Attachments: SOLR-3658.patch
>
>
> see mailing list http://markmail.org/thread/yy5b7g6g7733wgcp
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
