Skip to main content
Announcements
Qlik Community Office Hours, March 20th. Former Talend Community users, ask your questions live. SIGN UP
cancel
Showing results for 
Search instead for 
Did you mean: 
markmccoid
Partner - Creator II
Partner - Creator II

Publisher Reloads Fast, But Distribution to Server Mount SLOW

I've got Publisher installed and running on a server.  It reloads my 400 Meg file in a couple of minutes, but then takes close to 20 minutes to distribute the file to the server mount that I have set up in the "Distribute" tab in the Publisher Task.

I have see a couple of other post about this, but no response as to a resolution.

Has any one had this issue and found a fix or is it a "bug".

14 Replies
gainkarthi
Partner - Specialist
Partner - Specialist

You have QVS in different server. Have you encountered same slowness while copying for Publisher machine to Server mount folder ?

markmccoid
Partner - Creator II
Partner - Creator II
Author

I actually have the both the mount folders and the Source document folders on the Publisher machine.

I've tried copying the files manually to see how a simple copy works and that is like copying a normal file.

QV support has suggested looking at Virus programs or automatic backup application that may be slowing it down.  I will be testing that today.

gainkarthi
Partner - Specialist
Partner - Specialist

Also please check the memory and CPU usage while slowness occurs.

markmccoid
Partner - Creator II
Partner - Creator II
Author

I have checked this and CPU never goes over 50% and memory usage is 8 gigs out of 64.

I find it strange that it takes the same amount of time to distribute the file each time.  I would think that if it were memory or CPU related, I would see the distribution times changing each time.

Have you seen the distribution of a large file (Over 300 Meg) happen in less the 5 minutes?

Thanks

Not applicable

What kind of distribution are you doing?

If you have put any loops, reducation, section access reducation, then this will and can take time.

In those cases, you can´t compare a basic copy - paste with a distribution.

How many users are you distributing to? This also have effect on distribution.

markmccoid
Partner - Creator II
Partner - Creator II
Author

Hi Andreas,

Just distributing to a mounted folder.  It is only creating one QVW file for distribution.  There are no loops and reduce steps and while we do have section access, this is in the QVW and is not done (at least I'm assuming it isn't) done by the publisher distribution task, but instead when the file is initially loaded.

I'm distributing to all authenticated users.

I do notice that the larger the file, the longer it takes.  This is because the writing of the file is slow.

What size are the files you are distributing

Not applicable

Hi Mark,

Try having the folders and the storage disks regularly defragmented.

Fragmentation can cause serious issues related to file handling. It wont show up anywhere on your CPU loads or Memory but it will always slow down your machine.

Hope this helps,

Abhinava

marcohadiyanto
Partner - Specialist
Partner - Specialist

anyone know how to solve this?

it happen to me too..

i have 1 qlikview server and 1 qlikview publisher, its on separate machine.

i try distribute 1 qvw no reload no reduce no loop, it takes 30 min but when i copy manually this qvw it doesn't take 30 min.

*qvw size 1GB

Anonymous
Not applicable

Mark

Refer to this post http://community.qlik.com/thread/64731

Below  I have posted from my reply the the thread and attached the attachment.

It may or may not be relevant to your issue.

I had exactly the same issue and it was resolved by Windows update 2600217, as per Andreas 's earlier post.


The attached pdf gives more details.  It is on the QlikView web site, but I won't put the url in due the Moderation Quagmire.


I first applied all the latest Windows updates before the patch.


BEWARE:    We had not applied Windows Updates since early last year and they took the best part of 2 hours to run and fair few reboots, which was a bit embarrassing and I had advised only a one hour outage.



Best Regards,    Bill