z-logo
Premium
Metabolomic and 13 C‐metabolic flux analysis of a xylose‐consuming Saccharomyces cerevisiae strain expressing xylose isomerase
Author(s) -
Wasylenko Thomas M.,
Stephanopoulos Gregory
Publication year - 2015
Publication title -
biotechnology and bioengineering
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 1.136
H-Index - 189
eISSN - 1097-0290
pISSN - 0006-3592
DOI - 10.1002/bit.25447
Subject(s) - xylose , xylose isomerase , biochemistry , xylose metabolism , fermentation , pentose , saccharomyces cerevisiae , chemistry , metabolic engineering , pentose phosphate pathway , isomerase , glycolysis , metabolism , enzyme , yeast
Over the past two decades, significant progress has been made in the engineering of xylose‐consuming Saccharomyces cerevisiae strains for production of lignocellulosic biofuels. However, the ethanol productivities achieved on xylose are still significantly lower than those observed on glucose for reasons that are not well understood. We have undertaken an analysis of central carbon metabolite pool sizes and metabolic fluxes on glucose and on xylose under aerobic and anaerobic conditions in a strain capable of rapid xylose assimilation via xylose isomerase in order to investigate factors that may limit the rate of xylose fermentation. We find that during xylose utilization the flux through the non‐oxidative Pentose Phosphate Pathway (PPP) is high but the flux through the oxidative PPP is low, highlighting an advantage of the strain employed in this study. Furthermore, xylose fails to elicit the full carbon catabolite repression response that is characteristic of glucose fermentation in S. cerevisiae . We present indirect evidence that the incomplete activation of the fermentation program on xylose results in a bottleneck in lower glycolysis, leading to inefficient re‐oxidation of NADH produced in glycolysis. Biotechnol. Bioeng. 2015;112: 470–483. © 2014 Wiley Periodicals, Inc.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here