Jeff
> --
> You received this message because you are subscribed to the Google Groups "Alfresco Technical Discussion" group.
> To post to this group, send email to alfresco-techn...@googlegroups.com.
> To unsubscribe from this group, send email to alfresco-technical-d...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/alfresco-technical-discussion?hl=en.
>

Are you noticing the same thing when you browse through WebDAV/CIFS?
I should point out that our recommendation is to not put more than a few thousand files in a folder. Though the repository can handle more than that many children in an association, whenever a list has to be enumerated (browsing the folder tree), there will be a performance hit with so many children.
When so many files are required in your information architecture, it usually works better to hash your files into an arbitrary folder structure and use the category taxonomy to browse.
Richard
On Tuesday April 3 2012 17:21:41 Craig Nelson <craig.mich...@gmail.com> wrote:
> Hi,
> I got some help from another mailing group who told me that all i need
> to do is to change the system.filefolderservice.defaultListMaxResults to a
> higher number. The default from the repository.properties is 5000 hence why
> i couldn't see more than 5000 files. I changed it to 100,000 and now it is
> working.
>
> On Tue, Apr 3, 2012 at 5:12 PM, Craig Nelson <craig.mich...@gmail.com
> > wrote:
>
> > This is what we are doing.
> > Running 93 instances of an upload web scripts 8 clients to move thousands
> > of files into the user home of a single user. We noticed that when we go to
> > explorer under Company Home/User Homes/Person's User Homes that we will be
> > presented with a list of 9 in the view and we can scroll over to 556 page.
> > If we manually upload the file we wont see it. It is like we are putting
> > the files into a black whole. Here is what it looks like from the explorer
> > page. We were also able to change the company home of this user while the
> > clients were running and it started to put the files into the new folder.
> > We are also not seeing any errors in our catalina.out nor in our
> > alfresco.log file.
<snip>