We're sorry GroupDocsCloud doesn't work properply without JavaScript enabled.

Free Support Forum - groupdocs.cloud

Credit Calculation issue using GroupDocs.Merger Cloud Docker with Google Cloud Storage

GroupDocs.Merger Cloud Product Family
#1

Hi @tilal.ahmad

We’ve implemented the Google Cloud Storage support you’ve added for self-hosted docker instances, and it seems the credit increase bug is back. Here are the outputs and logs from some test runs for merging two pptx files:

  • run 1: 666 credit increase
    image.png (13.5 KB)
    image.png (13.5 KB)
  • run 2: 666 credit increase
    image.png (13.5 KB)
    image.png (13.5 KB)
  • run 3: 666 credit increase
    image.png (13.0 KB)
    image.png (42.3 KB)
  • run 4: 479 credit increase (two files different from previous runs)
    image.png (13.3 KB)
    image.png (29.8 KB)
  • run 5: 445 credit increase for first error + 446 credit increase for second error (two files different from previous runs)
    image.png (121.7 KB)
    It seems we get an exception because we’re exceeding the memory limit:image.png (7.7 KB)
    Are the files collected from Google Cloud Storage not deleted after merging? And if so, could it be made so that they are deleted (as we don’t want an ever increasing container)?

Could you please fix this bug? Thanks.

Self-hosting: credit system issue
Self-hosting: credit system issue
#2

@mixonfreddy6plus

We are sorry for the inconvenience. We have logged a ticket MERGERCLOUD-63 to investigate and fix the issue. However, we will appreciate it if you please share your sample files with us as well.

#3

@mixonfreddy6plus

We have made some memory usage improvements in GroupDOcs.Merger Cloud Docker Container and uploaded to DockerHub. You may please test it.

Furthermore, we cannot reproduce the credits issue. As requested earlier, please share your sample documents with us. Thanks for your cooperation.

#4

Hi @tilal.ahmad,

Here are the sample presentations I used which got me the results above:
https://we.tl/t-J4UOwxKkQ1

Thanks.

1 Like
#5

@mixonfreddy6plus

Thanks for sharing your sample documents. It will help us to test the credit calculation issue. We will share our findings with you as soon as possible.

#6

@mixonfreddy6plus

We have joined your provided 6 files into one, and it took just 5 credits for that, although memory consumption was greater than 1 GB. We will continue investigating it.

Regarding unreasonably high credits consumption, we will appreciate it if you please test the latest version of GroupDocs.Merger Cloud that was published at DockerHub and confirm the result because it was fixed there.

#7

Hi @tilal.ahmad

Thanks for your response. It seems we had a version update issue, we did some tests and we found the credit consumption to be correct. However, like you stated, we did hit our 1 GB memory limit once we tried merging 4 of our sample presentations.

Thanks.

#8

@mixonfreddy6plus

Thanks for your feedback. It is good to know that credit consumption issue is resolved.

We are investigating the memory consumption issue. It is related to our underlying on-premise API. We will update you as soon as we made some significant progress towards the issue resolution.

As for now, it is recommended to increase memory size to 4GB of Docker image, for the provided files.