It took 2.5 hours to update the marking scale. So the question is not "failed"
but one of "delayed" updating of marking scale.

• I removed the \AMCcodeBoxSep line, with has been dropped in the new style version, even if the doc still mention it — this has to be corrected.
• With this new style version, the layout has been changed a little, so automatic data capture is not correct with your scan.
  With my computer, updating marking scale is faster than generating documents (~2 min).

Thank you for the same! I shall keep this in mind for future projects.

To extract the marking scale from the source file, AMC runs LaTeX once and reads some log file. To build the documents, AMC runs LaTeX one or more times (more than once if your documents needs re-run due to labels, or if you asked for the solution or catalog document). So updating the marking scale should be faster that generating documents, and your situation seems very strange to me. Is it the same for a moderate amount of copies from the same source file? If so, can you update the marking scale in debugging mode, and join the log file?

Dear Shreikant and Alexis:

This issue makes me remember this: AMC performance on postcorrection

I seems that, under some specific scenarios, ACM becomes slow when the marks scale is updated. The problem here is to identify exactly what are the conditions that make AMC to become slow when this task is carried on. If I can help with testing or something else, please let me know and I'll see how I can colaborate with this.

Regards.

You are right: I would like to reproduce the problem, so that I can investigate and (I hope) fix it. Unfortunately, untill now I could not. so I am a little puzzled.

Commenting out the lines:

%\AMCcodeHspace=.5em
%\AMCcodeVspace=.2em
%\AMCcodeBoxSep=.1em

Thanks to Alexis for pointing this out.

Did you also update AMC? I think commenting the last line is necessary to use development version of AMC, but the reason why all is faster now is that you updated AMC, not that you commented out some of these lines. The opposite would be very weird to me.

No, Alexis. I could not update AMC. I am still with 1.2.1 (svn 1403).
Yes, commenting these lines worked like magic.

(I have Ubuntu 12.04 -- tried to update AMC to development version-- but
got some broken packages. Couldn't quickly fix the problem).

Also, Alexis, when I run from command line with a debug file,
where is the log file placed? Thanks.

So this is very strange!

when I run from command line with a debug file, where is the log file placed?

You can specify the file to add log to with --debug file.log

I guess I have found the problem. When I had version x of AMC, I could not
run input latex files as the "automultiplechoice.sty" was not found. (Due
to nature of tex installation). I moved the version x latex style file
to ~/texmf/tex/latex".

After a while I upgraded AMC to version y. But now owing to nature of tex
installation, AMC Version-y was using latex style file Version-x.

I do not know whether "Update Documents" and "Extract Marking Scheme" match the
version of AMC with the latex style file: and if not it might be worth it to
put this check.

No wonder this problem persisted for months and years.....

I do not know whether "Update Documents" and "Extract Marking Scheme" match the
version of AMC with the latex style file: and if not it might be worth it to
put this check.

Not yet. I agree this should be a good thing. Can you add a feature request?