# any solution for this issue even after i've changed batch size its not working **URL:** \ **Category:** Uncategorized\ **Tags:** usage, spacy, training, spancat\ **Created:** [June 20, 2022, 1:17pm UTC](https://support.prodi.gy/t/any-solution-for-this-issue-even-after-ive-changed-batch-size-its-not-working/5717 "2022-06-20T13:17:22Z")\ **Posts on this page:** 1\ **Showing post:** 8
**Author:** ![koaning](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/koaning/32/230_2.png) [@koaning](https://support.prodi.gy/u/koaning)\ **Post date:** [June 22, 2022, 8:41am UTC](https://support.prodi.gy/t/any-solution-for-this-issue-even-after-ive-changed-batch-size-its-not-working/5717/8 "2022-06-22T08:41:53Z")
Please put code/tracebacks in code blocks (by wrapping them in ```). That way, it's easier to look through them and they will also become scrollable, saving screen real estate. It's becoming more and more clear that this is perhaps less of a Prodigy issue and more of a spaCy/Pytorch issue. One question, a span of size 96 feels very large. Are you using a custom config? Your previous commands suggested that you weren't and the standard config has these span sizes: ```python [components.spancat.suggester] @misc = "spacy.ngram_suggester.v1" sizes = [1,2,3] ``` Is there a reason why your span size really needs to be that big? --- _[View the full topic](https://support.prodi.gy/t/any-solution-for-this-issue-even-after-ive-changed-batch-size-its-not-working/5717)._